Posted by mes_backlab on July 27, 2018 at 11:23am
Is there a particular reason Open Atrium sticks with Ultimate Cron 2.0?
I spent quite some time googling around the issue of "X jobs are behind Schedule" on the Status Report Page until i found this: https://www.drupal.org/node/2949059/revisions/10860598/view
Since I'm running Open Atrium on PHP7 i just tried manually updating Ultimate Cron to 2.5 and now Report states "Cron is running properly". So far no other problems on the site.
Categories: behind schedule, ultimate cron