HangfireIO / HangfireIO/Hangfire
Hangfire Jobs Failing and StateName = NULL in Hangfire_Job table
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Hello,
I previously scheduled a job in Hangfire, and it had been running smoothly for an extended period. However, recently, I encountered an issue where jobs started failing (after I restarted the EKS Pod). Upon investigating the Hangfire_Job table, I noticed that the jobs being added in Hangfire_Job table were missing values for StateId and StateName (having null values for both columns). Previously, these fields had valid IDs and names associated with them.

Contributor guide
Research direction
Start by reviewing the Hangfire_Job table entries created after the EKS Pod restart and compare their null StateId and StateName values with earlier successful jobs. Use the issue's failure scenario to trace what happens during job creation and determine what must change so new jobs receive valid state values and stop failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100