UPDATE (2015-10-29) ---- Original issue summary can be found in the revisions
------------
The cron lock time can be outrun by the max execution time.
A recent patch to the Drupal core → enabled the possibility to have PHP scripts for a very long time, because the max_execution_time is not updated if it has been 0 before.
Still the hard coded value for the cron lock is 240 seconds. The problem with that is, that a cron, that runs over this amount of time is not cancelled, which is fine, of course, because some of them just take time.
That way a cron can be executed multiple times simultaneously which would trigger a lot of queue processing.
Closed: outdated
7.0 ⚰️
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thanks for working on this. I think this was fixed by #3308929: [D7] Cron lock time limit is too short and does not prevent multiple, concurrent cron runs → . Cron lock is no longer a fixed value, instead its value is from a variable. Feel free to reopen if this is still an issue.