HangfireIO / HangfireIO/Hangfire

Hangfire.Pro multiple continuations - batches can be stuck in the Started state

Open
#2,080 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
10.1k
Forks
1.8k
Avg merge
1h 19m
Merged PRs (30d)
1

Description

I have some strange issue; after some uptime hangfire do not picking up the jobs.

Server have the X workers but the amount of processing jobs is 0 or lower than X.

In the same time I see Batch is pending because it's dependent on other Job that is in Enqueued status, when I requeue this job then it unstuck it.

I also see that in the Queues view, for example, some queue have Fetched Jobs = 3, but when I inspect it all the 3 jobs are Succeeded like 4 days ago.

I can't pinpoint this to a single change on our side, we are using Hangfire 1.7.30 and 1.8 newest RC in various combinations (SQL Server or Memory Storage) and the issues are the same.

We have Startup subscription.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or code entry points are named. Start by reproducing the stalled batch and queue state with Hangfire 1.7.30 or 1.8 RC using SQL Server or Memory Storage; done means continuations leave Started or pending states and fetched-job counts no longer remain stale.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, sql
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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.