How QCTNH Drains Multiple Due Tasks Safely

Because native Joomla WebCron processes work one execution opportunity at a time, QCTNH can issue bounded follow-up calls when the fresh scheduler snapshot shows that more tasks are already due.

Backlog-drain behavior

After a successful wake-up, the worker reloads the central site row. If the post-WebCron outbound check-in updated next_due_at and that time is still due, more_due becomes true.

Fast follow-ups

Inside the same worker run, a successful result with more due work can be queued for another attempt about two seconds later. The stored central next-poll calculation uses a small five-second backlog interval, providing another bounded opportunity if the current worker cycle ends.

Joomla still serializes actual work

Every follow-up is another native WebCron request; QCTNH does not loop through task IDs itself. Joomla’s locks and Scheduler logic continue to protect execution.

Identity and timing are both required

For How QCTNH Drains Multiple Due Tasks Safely to work safely, QuantaCade needs both a valid registered identity/endpoint and useful scheduler timing. A perfectly known next-due time is not enough if the site origin or WebCron credential is invalid; a perfect connection is not enough to schedule intelligently if Joomla has no eligible task timing.

Test Connection focuses on identity/public reachability, while task-change/WebCron-completion check-ins keep operational timing current.

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.