Using Check WebCron
Check WebCron is the safe local-readiness action: it prepares/verifies Joomla WebCron configuration but does not send a WebCron execution request.
Run Check WebCron
- Open QCTNH → Dashboard.
- Click Check WebCron.
- Read the Joomla message. A successful result says WebCron is enabled and ready and explicitly states that no Scheduled Task was executed by the check.
What it checks/repairs
- System - Schedule Runner exists and is enabled.
- The Joomla Scheduler component exists.
- WebCron is enabled.
- A WebCron key exists; one is created if needed.
- The current Joomla-generated native WebCron endpoint can be built.
What it does not test
It does not prove that QuantaCade can reach the site from outside, does not register/adopt a migration origin, and does not call WebCron. Use Test Connection for the end-to-end service path.
Use the Dashboard as a cross-check
The control or metric covered by Using Check WebCron is most useful when read beside the other Dashboard evidence. Connected status alone does not prove a particular task is healthy, and a Due count alone does not prove the wake-up service is broken. Compare WebCron readiness, lock counts, next/oldest timing, QuantaCade Contact, and Recent Activity before drawing a conclusion.
That combined view usually tells you whether the next action belongs in Joomla Scheduler, QCTNH service configuration, networking/WebCron, or the extension that owns the failing task.
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.