HangfireIO / HangfireIO/Hangfire
Filter to remove failed jobs a few days (configurable) after a newer instance of same job succeeds
Open
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
What would be an appropriate pattern to implement a job filter such that it sets the expiration wen/once a subsequent instance of the same job succeeds.... i.e. auto-expire failed jobs once the job runs successfully again.
Contributor guide
Research direction
No file, test, or entry point is named. First identify Hangfire's job-filter and expiration extension points, then determine how to recognize a later successful instance and expose the expiration delay as configuration. Done means failed jobs are automatically expired after a configurable delay when a newer instance of the same job succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100