How exactly Job TTL feature works on Active and Inactive jobs ?
Open
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Could someone explain clearly how the **Job TTL** treat on **Active** and **Inactive** jobs ?
Thank you :)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Job TTL implementation and any existing documentation for active and inactive jobs; the issue names no file, test, or entry point. Compare the documented behavior with the implementation, then document clear TTL semantics for both job states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- backend, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100