I know that sidekiq removed the timeout functionality long ago so I am wonder if there is something else that does that limits the run time of jobs. Here is what I am doing and what I am experiencing. I have two jobs that run in the low que and they take about 5 to 10 minutes to run. When they complete the ‘Last Result’ is listed as OK but the ‘Last Duration’ is listed as blank. So I am asking this because I want to be sure it is really completing and secondarily I would like to know what the runtime in production generally looks like. I only can estimate from my dev instance with all the same data imported. I have one other jobs that runs in the same que and is quick. It has it’s ‘Last Duration’ listed.
What are the jobs for those that are wondering?
For reasons that I will not got into, other than not real IDM, I have a plugin that invasively managed the membership of two discourse sites via a plugin. There are two long running jobs that provision/repair accounts and a second one that deactivates accounts of people that have left. There are generally about 7,000 active accounts. In both cases they compare the reality of the instance against the reality of the feed from our ERP.