What QCTNH Does When Exact Next-Due Timing Is Unknown

If the site cannot provide an exact next-due time, QCTNH falls back to bounded service timing rather than assuming no work will ever be needed.

When timing can be unknown

• There are no eligible web-runnable tasks with a non-NULL next execution time.
• A fresh post-WebCron snapshot has not yet arrived.
• Scheduler discovery encountered a transitional condition.

Fallback behavior

For ordinary states without a useful next-due timestamp, the central service can use the configured Maximum Scheduler Delay. After an idle/ran result with no known next work, the service can sleep until the six-hour safety recheck instead of polling every few minutes.

Unknown is not automatically unhealthy

The Dashboard may show Waiting / unknown for Next Eligible Task while Scheduler Health remains Healthy. That combination can simply mean there is currently no predictable WebCron work.

Why the service can stay quiet

The mechanism in What QCTNH Does When Exact Next-Due Timing Is Unknown 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.