Distinguishing a Scheduled Task Failure from a Task Nudge Service Failure
A Scheduled Task failure and a Task Nudge service failure occur at different layers and require different troubleshooting.
Distinguish the layers
| Evidence | Interpretation |
|---|---|
WebCron HTTP 2xx but Joomla JSON says success:false | The transport reached Joomla, but the scheduled task/application reported failure. Investigate the owning task/extension. |
| WebCron HTTP 5xx | Worker classifies it as task_failed; inspect Joomla/PHP/task error output. |
| HTTP 401/403/404 or DNS/TLS/connection error | Service/WebCron reachability/authentication/route problem rather than proof of extension task failure. |
| QCTNH Error health before a run | Local scheduler snapshot/discovery problem. |
Why the distinction matters
Re-registering QCTNH will not fix a backup plugin throwing an exception, and debugging the backup plugin will not fix a WAF returning 403 to WebCron. Start at the layer identified by the status code and message.
Do not “fix” the metric directly
The correct response to Distinguishing a Scheduled Task Failure from a Task Nudge Service Failure is to resolve the underlying Joomla state, not edit QCTNH’s displayed value. Due counts change when Joomla advances task schedules; locks change when tasks start/finish or are safely recovered; contact times change after authenticated service communication.
Manual database edits to make a Dashboard number look better can hide the real scheduler problem and are not part of normal QCTNH operation.
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.