Troubleshooting a Quiet Site That Is Not Being Awakened

If a quiet site is not being awakened, first prove that QCTNH is registered and enabled, then separate service scheduling from Joomla’s own task eligibility.

Service checks

  1. Dashboard must show Connected.
  2. The free Task Nudge service checkbox must be enabled, not paused.
  3. WebCron must report ready.
  4. QuantaCade Contact should not be permanently “Not yet.”
  5. Recent Activity should not show repeated sync/registration/network errors.

Scheduler checks

  • At least one enabled, non-CLI-only Scheduled Task must have a usable next_execution.
  • The task type must still exist in Joomla’s currently registered Scheduler routines.
  • If no task is due and the next due time is known far in the future, QCTNH correctly sleeps rather than waking repeatedly.

Force a diagnostic safely

Use Check WebCron for local readiness. Use Test Connection only when you are prepared for a real WebCron probe that may execute one due task. After a successful check-in, compare the Dashboard next-due state with the task’s Joomla Scheduled Tasks entry.

Diagnose from the outside in

For Troubleshooting a Quiet Site That Is Not Being Awakened, a reliable order is: local Joomla prerequisites → QCTNH WebCron readiness → public DNS/TLS/route → WebCron authentication → Joomla Scheduler/task result. Each layer produces different evidence, so skipping directly to reinstalling QCTNH often obscures the real cause.

Use Check WebCron for the local layer and Test Connection for the full public registration/probe layer. Then use Joomla/extension logs if the request succeeded but the task itself failed.

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.