Job timing out with the error "moving jobs to failedjobregistry (work-horse terminated unexpectedly) no PID returned"

[maevecnorton]

I have read that that error message usually means some memory issue but that doesn't seem to be the case for me.
I have a scheduled job that runs forever where each run takes about 6 minutes to run. Scheduler.schedule function is called with interval set to 600 and timeout set to 600. The job gets queued every 600s which is fine but what seems to be happening is that my job seems to time out after 600 seconds of total execution time across ALL runs. Since each run is about 6 minutes, during my second run, the job times out and the job fails and it has the same error ever since.

Is this how timeout should work? What do I do if I don't want any timeout so that my scheduled job can actually run forever every 600 seconds?

If I set timeout to none, in redis monitor I see that timeout gets defaulted to 180. I guess I can set the timeout to something insanely long but that doesn't seem like a good solution and it will eventually hit the timeout.

Any help would be appreciated!