We had an issue where cron would reach max_execution_time and simply stop. The issue was that we did not know which module's cron tasks were taking so much time, thus added more logging for cron runs to identify slow modules.
We realize that this might be solved using modules like Ultimate Cron (or maybe some other?), however, it seems overkill to have to install a new module for these small changes. For example, you are using standard cron and you encounter the same issue. And, let's say that the longest task is search indexing. You can simply change the setting to have less pages indexed once you know why it reaches max_execution_time.
Other idea would be to add more hooks to cron runs, so the users could develop more flexible solutions without altering Drupal core.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
No activities found.