AnsweredAssumed Answered


Question asked by Francesca Shiekh on Nov 10, 2015
Latest reply on Nov 10, 2015 by Tim Turnquist
From the manual:…
DescriptionDetermines the maximum time in seconds that a single job should be allowed to run. If a single job exceeds this limit, cron.php is aborted with the long-running job marked as in progress in the job queue. The next time cron runs, it will skip the job that overran the limit and start on the next job in the queue. This limit is only enforced when cron.enforce_runtime is set to true.


I don't see a counterpart in the documentation for 7.x so I assume this still applies to v7.


I don't quite understand if the long-running job marked as in progress continues to run or is killed when the cron.php is aborted.

Can someone explain this parameter and how it impacts the cron frequency?