How QCTNH Treats Disabled Scheduled Tasks

Disabled Joomla Scheduled Tasks are excluded from QCTNH’s web-runnable due and next-due calculations.

Current rule

The scheduler snapshot begins with state = 1. A disabled task therefore cannot make QCTNH show Due, cannot become the Next Eligible Task, and cannot drive a QuantaCade wake-up schedule.

When you disable a task

The QCTNH System plugin listens for Scheduler task state changes. After a Scheduled Task is enabled/disabled, it sends a check-in so QuantaCade can refresh timing rather than continuing to operate from stale next-due information.

Verification

  1. Open System → Scheduled Tasks and disable the test task.
  2. Return to QCTNH Dashboard and allow the state-change check-in/refresh.
  3. Confirm the task no longer contributes to the Due Tasks count or Next Eligible Task timing.

Execution boundary

For How QCTNH Treats Disabled Scheduled Tasks, remember that one WebCron request is an execution opportunity, not a command to run a named task. QCTNH never sends a task ID to force selection. Joomla receives its normal System - Schedule Runner request, applies its queue/lock/recurrence rules, and returns the result of the work it chose.

This design is why QCTNH can work with Scheduled Tasks from many extensions without knowing their business logic. It also explains why a task-specific error belongs first to the owning extension even when QCTNH successfully delivered the WebCron request.

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.