inactive job keeps firing
Open
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
how did a job get to inactive ? and once it does, it will keep firing it non stop ? how to we stop it ? how do we even recognise this job was marked as inactive and then we can maybe deal with it differently
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by reproducing the inactive-job behavior and tracing the job lifecycle in Kue; done should include a confirmed explanation of why the job keeps firing and a documented or tested way to recognize and stop it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100