catch ttl exceeded
Open
Feature
needs pull request
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Is there a proper way to know when a job has exceeded its ttl and it failed? All the following events I tried are not being fired when a job fails due to ttl:
### events on the job
- failed
- remove
### events on the queue
- job failed
- job remove
Using kue version 0.9.5
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing a job that exceeds its TTL in Kue 0.9.5 and inspect how the job and queue failed/remove events are handled. Confirm the expected notification path and add coverage demonstrating whether the relevant event fires when TTL expiration causes failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100