Maximum Scheduler Delay Values Reference
Maximum Scheduler Delay accepts five values—5, 10, 15, 30, or 60 minutes—and controls fallback/safety timing when QCTNH cannot schedule purely from an exact known future next-due time.
Allowed values
| Minutes | Typical use |
|---|---|
| 5 | Time-sensitive web-runnable tasks where a small fallback delay is important. |
| 10 | Balanced default-style responsiveness for many sites. |
| 15 | Moderate tolerance for non-urgent maintenance. |
| 30 | Lower wake-up frequency for less time-sensitive sites. |
| 60 | Largest supported delay; suited only when an hour of fallback latency is acceptable. |
It is not a fixed poll-every-N-minutes timer
When QCTNH knows a future next_due, the central scheduler can sleep until that time plus a small jitter, subject to a six-hour safety recheck. Immediate backlog/busy/failure conditions have their own bounded follow-up timing. Maximum Scheduler Delay is primarily a fallback/unknown-timing tolerance, not a guarantee that QuantaCade requests your site at that exact interval forever.
Reference verification
When checking Maximum Scheduler Delay Values Reference on a live site, prefer observable 2.0.3 state: QCTNH Dashboard/Status, Joomla Scheduler and Schedule Runner configuration, Recent Activity, and owning-extension logs. Internal tables/endpoints are reference material and should not be edited/called casually just because they exist.
This keeps normal administration on supported UI paths while still giving advanced administrators enough detail to understand what the product is doing.
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.