- 🇧🇪Belgium lisotton Brussels
I have a similar case. I have many jobs configured and the most frequent ones are configured to run every 15 minutes. I have the system cron calling the drush command every 5 minutes, but still in the Status Report page I have, from time to time, jobs being reported as behind schedule. In the list of jobs, as you can see in the attached screenshot, the first job in the list had ran at 10:25 and now is 10:36 and it is already reported as behind schedule:
I think a job should be reported as behind schedule only if the last run is more than 15 minutes ago, if the job is configured to run every 15 minutes. In this case, it has passed 11 minutes and the job is already reported as behind schedule.
- Merge request !69Issue #2951974: Do not report Simple jobs as behind if they ran within the configured interval → (Open) created by lisotton
- 🇧🇪Belgium lisotton Brussels
I have worked in a MR that do not report Simple jobs as behind if the last run was within the configured interval. For example, if a job is configured to run every 15 minutes, it will be reported as behind only if it is more than 15 minutes since the last run.
This will clear the warning in the Status Report page.
- 🇵🇹Portugal crgomes
I have the same issue #6 🐛 ultimate cron cron jobs are running fine but status report page shows, some jobs are behind schedule Active as described by lisotton → . I've tested the patch from the merge request #7 🐛 ultimate cron cron jobs are running fine but status report page shows, some jobs are behind schedule Active it and it is working fine. Thanks lisotton → .