I have a strange issue. We have Hangfire deployed to several of our environments. It works 100% perfectly in our Production environment. However in our UAT environment when we enqueue a job, the Dashboard reports success, but the job (which should take around 10 minutes to complete) completes “successfully” in milliseconds. When I check for any of the SQL database changes that the job should make, I can see it has in fact done nothing, despite reporting successful execution.
I know it’s not a code issue. I can point my UAT code-base at the UAT SQL Server and run the whole job through in debug and it enqueues the job correctly and then runs the enqueued job 100% perfectly. So I have a situation where:
- a job enqueue works locally in debug against my UAT server.
- the same job works in a deployed copy of the application on my Production server
- yet that same job reports “success” but does nothing on my UAT server.
It feels likely to be a UAT server config issue, but I don’t know where to start looking on that front. Any suggestions (or maybe it’s not a server config issue)?