HangfireIO / HangfireIO/Hangfire
Hangfire.Pro Redis Invisibility timeout issues.
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
We are continuing to get invisibility timeout issues.
There are times that the job gets the timeout and dies the first time, and then on the retry, there is no invisibility timeout.
In another instance, the job appeared to complete the first time, but got an invisibility timeout, retried, and then without completing was somehow marked as complete.
We are using the following versions:
Hangfire.Core 1.6.14
Hangfire.Console v1.3.3
Hangfire.Pro v.2.0.1
Hangfire.Pro.Redis 2.1.1
Which I believe are all the latest release for each!
Thanks!
Contributor guide
Research direction
The report names Hangfire.Core, Hangfire.Console, Hangfire.Pro, and Hangfire.Pro.Redis versions but no source files, tests, or reproduction steps. Start by reproducing the invisibility-timeout and retry behavior with these versions, then trace the Redis job lifecycle. Done means identifying the cause and verifying that timed-out retries cannot be incorrectly marked complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100