How Scheduled Task Changes Refresh QuantaCade Timing
QCTNH listens for Joomla Scheduled Task changes so QuantaCade timing can be refreshed immediately after an administrator changes the queue.
Changes QCTNH watches
| Joomla event | QCTNH check-in reason |
|---|---|
| Task created | task_created |
| Task saved | task_saved |
| Task deleted | task_deleted |
| Task state changed | task_state_changed |
| Scheduler component configuration saved | Synchronizes the WebCron registration with reason joomla_webcron_config_saved. |
Why immediate refresh matters
Without this event-driven check-in, the central service might retain an old future next-due time after you add an earlier task, disable an overdue task, or change scheduler configuration. Sending a fresh snapshot keeps wake-up timing aligned with Joomla.
Why the service can stay quiet
The mechanism in How Scheduled Task Changes Refresh QuantaCade Timing is designed to minimize needless traffic. Once QuantaCade has a trustworthy future next_due, it can schedule the next useful check near that time with small jitter and a bounded safety recheck rather than polling the Joomla site every few minutes indefinitely.
Fresh state after WebCron completion is especially valuable because it tells the worker whether more work remains due, a later future task is known, or the site can safely sleep.
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.