Job is stucking in enqueue state

bug? moved to github
,
1

I have added a job in enqueue and it is stucking there. I am using redis as storage. When I requeue from dashboard it processed the job successfully. Kinldy help in this regard.

1.png1203×402 20.7 KB
2.png1261×971 49.3 KB

2

I am having the same problem It appears, when resolved from Unity and then sent to a Queue that it ALWAYS defaults to the DEFAULT QUEUE even when marked with another queue. You can see my code at:

http://hangfire.discourse.group/t/jobs-in-enqueue-state-most-never-run-sql-only/2367

After running it appears stuck in the default queue:

Queue001.PNG1158×562 31.8 KB

I do the same as @abdulbasit (Requeue via dashboard) and it runs:

Queue002.PNG1153×798 37.6 KB

This is driving me nuts! :slight_smile:

3

@abdulbasit, never use the following construct, as it even does not make any sense, because of unnecessary creation of the Job class instance.

// Don't do this at home
var job = new Job();
BackgroundJob.Enqueue(() => job.Execute());

if you are using instance methods, always use the .Enqueue<T> method overloads:

// This is for instance methods
/// Place [Queue] attribute to the IJob.Execute method
BackgroundJob.Enqueue<IJob>(x => x.Execute("payload"));

// This is for static methods
BackgroundJob.Enqueue(() => Program.Main());
4

Reported to GitHub, please GitHub issues to discuss the bug, and this topic for other discussions.