Troubleshooting Scheduled Tasks That Still Run Late
A Scheduled Task can still run late even with QCTNH if it is ineligible, CLI-only, locked, failing, the service is paused/disconnected, or the configured Maximum Scheduler Delay allows the observed lag.
Work through the causes
| Observation | Interpretation / next check |
|---|---|
| CLI-only Tasks includes the task | QCTNH WebCron intentionally cannot run it; use CLI/server cron. |
| Soft / Stale Locks > 0 | A stale scheduler lock may be preventing normal selection; investigate the owning task/process. |
| Active Locks > 0 / Health Working | Joomla believes task work is currently locked/running. |
| Task type no longer registered | Orphaned row is excluded from QCTNH eligibility; repair/uninstall the owning extension/task row. |
| Not Connected or service paused | External wake-up path is unavailable. |
| Maximum Scheduler Delay is 60 minutes | Unknown-timing fallback can intentionally wait longer than a 5-minute configuration. |
| WebCron returns task_failed | Transport reached Joomla, but task/application execution failed. |
Compare “due” correctly
QCTNH uses the database next_execution for eligible web-runnable tasks. Confirm server/database time and Joomla task configuration if the date you expect differs from what the Scheduler actually stores.
Preserve the failure evidence
Before attempting a repair for Troubleshooting Scheduled Tasks That Still Run Late, record the HTTP/status message, Scheduler Health, due/lock counts, WebCron state, QuantaCade Contact, and Recent Activity timestamp. For lock/task problems, also capture the owning Scheduled Task title/type and extension log.
That evidence lets you verify the fix and avoids converting a precise 401/403/404/task_failed condition into an ambiguous “it works now” report.
Troubleshoot lateness
- Open Joomla Scheduled Tasks and verify the affected task is enabled, web-runnable rather than CLI-only, and backed by a currently registered task routine.
- Compare its next execution time with QCTNH Due/Next Eligible status and inspect active/stale locks.
- Verify QCTNH is Connected, enabled, and WebCron Ready; then review recent WebCron/task results.
- If WebCron reaches Joomla but the task fails, move the investigation to the owning extension instead of changing QCTNH timing repeatedly.
Community Discussion
Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.