HangfireIO / HangfireIO/Hangfire
Hangfire doesn't reschedule/retry failed jobs on IIS
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Hangfire version is 1.7.8.
.Net version is 4.7.2
Use Sql Server
Set retry with `GlobalJobFilters.Filters.Add(new AutomaticRetryAttribute { Attempts = 1}); `. It works on visual studio, but not work after deployed to IIS 10 or 7.5.
On Visual Studio, the log file shows "WARN Hangfire.AutomaticRetryAttribute [(null)] - Failed to process the job '99846': an exception occurred. Retry attempt 1 of 1 will be performed in 00:00:16."
On IIS server, log file says "ERROR Hangfire.AutomaticRetryAttribute [(null)] - Failed to process the job '141223': an exception occurred."
Am I missing some config? Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported AutomaticRetryAttribute behavior under IIS 7.5 and IIS 10, comparing it with the Visual Studio logs for Hangfire 1.7.8, .NET 4.7.2, and SQL Server. Capture the full exception and relevant deployment configuration; done means identifying why retries differ and confirming retry logging and execution after deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100