Fixing WebCron Not Ready or a Missing WebCron Key

WebCron Not Ready or a missing key means Joomla’s native Schedule Runner is not yet prepared for authenticated remote WebCron execution.

Let QCTNH prepare it first

  1. Open QCTNH Dashboard.
  2. Select Check WebCron.
  3. QCTNH enables System - Schedule Runner if necessary, enables webcron.enabled, and creates a random 20-character Joomla WebCron key when none exists.
  4. Confirm the Dashboard WebCron field reports ready.

If the state immediately reverts

  • Another administrator/tool may be rewriting Schedule Runner settings.
  • A restore may be repeatedly replacing plugin parameters.
  • Database write failures may prevent the plugin params from persisting.
  • A security hardening rule may be preventing the core AJAX WebCron route.

Protect the generated key

Do not paste it into public diagnostics. If you intentionally regenerate it in Joomla, let QCTNH synchronize the new credential before expecting worker wake-ups to succeed.

Preserve the failure evidence

Before attempting a repair for Fixing WebCron Not Ready or a Missing WebCron Key, 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.

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.