I’m using hangfire 1.6.3 and pro.redis 2.0. From what I’ve read it seems that the invisibilitytimeout is causing my long running job to re-enqueue. Unfortunately, the job I’m dealing with may take up to 24 hours to complete. Raising the timeout that far would probably introduce other issues if the server is reset.
Is there any way I can introduce a heartbeat so the running job can let hangfire know it’s still alive thereby preventing the invisibilitytimeout from triggering?
Other info: this job can create hundreds of thousands of pdfs; each taking between 1-5 minutes. The job itself multithreads to process up to 32 concurrently. I can’t just have one job per report because a large customer (with 100k reports) would drown out a smaller customer (with only a few dozen). The goal is for it to remain fairly responsive to all customers even if that means leaving the servers involved slightly underutilized.