Troubleshooting Scheduler Health Stuck on Working

Scheduler Health remaining on Working means QCTNH continues to detect at least one enabled Scheduler row with a lock newer than Joomla’s timeout-derived stale threshold.

How Working is calculated

QCTNH uses Joomla Scheduler’s configured timeout, with a minimum safety floor, to divide recent active locks from soft/stale locks. A recent lock produces Working before Due/Healthy states are considered.

If Working lasts too long

  1. Identify which Joomla Scheduled Task is expected to be running.
  2. Compare its normal runtime with Joomla’s Scheduler timeout and the observed lock age.
  3. Check PHP/CLI/process logs and the owning extension for a long-running or hung operation.
  4. Do not clear the lock while a real process may still be active.
  5. If the lock ages beyond the threshold, QCTNH should transition it into Soft / Stale Locks and Health Attention.

QCTNH will not terminate the process

Its role is observation/wake-up, not process management. Resolve the owning task/runtime issue using Joomla/extension/server tools.

Diagnose from the outside in

For Troubleshooting Scheduler Health Stuck on Working, 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.