Troubleshooting Direct WebCron Service Errors
Direct WebCron service errors are failures to reach/authenticate/use the registered native Joomla WebCron endpoint, distinct from a Scheduled Task that actually ran and failed.
Examples
| Result | Layer |
|---|---|
| DNS/public-IP validation failure | Target discovery/security validation. |
| TLS error / no HTTP status | Network/TLS connection. |
| 401 | WebCron authentication/key drift. |
| 403 | WAF/access rule (with narrowly scoped same-server fallback possible). |
| 404 | Route/SEF/base-path mismatch. |
| Redirect | Final endpoint is not registered directly; worker does not follow it. |
Troubleshooting order
- Confirm Check WebCron succeeds locally.
- Confirm the final canonical URL/DNS/TLS is correct.
- Use Test Connection to reproduce the external probe and capture exact status.
- Inspect web server/CDN/WAF logs at that timestamp.
- Fix the transport/routing problem, then test again.
Confirm recovery at the same layer
After fixing Troubleshooting Direct WebCron Service Errors, verify the original failure signal specifically: a 401 should disappear after key synchronization, a 404 after route repair, a TLS error after certificate repair, a stale-lock Attention state after safe task recovery, and a task_failed result only after the owning task succeeds.
Then confirm the broader Dashboard state is coherent rather than treating Connected alone as proof that every Scheduled Task is healthy.
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.