Troubleshooting a Due Tasks Count That Looks Too High

A Due Tasks count that looks unexpectedly high means multiple eligible web-runnable task rows currently have next_execution at or before “now”; verify queue state before assuming QCTNH is double-counting.

What is counted

  • Task is enabled.
  • Task is not CLI-exclusive.
  • Task has a non-null next execution time.
  • Task type is among Joomla’s currently available scheduler routines when routine discovery succeeds.
  • Next execution is due now or earlier.

Common reasons for a backlog

  • Site was offline/quiet for a long period.
  • Service was paused or disconnected.
  • WebCron/network errors prevented wake-ups.
  • A locked/failing task held up queue progress.
  • A restore returned older scheduler timestamps.
  • Several different extensions legitimately scheduled tasks for the same interval.

Observe draining safely

After WebCron succeeds, Joomla advances/executed task state. QCTNH’s worker can make bounded follow-up WebCron calls when fresh state says more work remains due. Watch Due Tasks decrease and Recent Activity/owning-extension logs rather than manually editing next_execution.

Confirm recovery at the same layer

After fixing Troubleshooting a Due Tasks Count That Looks Too High, 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.

Validate the count

  1. Open Joomla Scheduled Tasks and identify enabled task rows whose next execution time is already due.
  2. Exclude CLI-only rows and any orphaned/unavailable task routines from your expected QCTNH web-runnable count.
  3. Check whether active/stale locks or prior service/network failures explain why multiple due rows accumulated.
  4. After successful WebCron execution, watch the due count and Joomla next-execution values advance instead of editing them manually.

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.