Understanding the CLI-only Tasks Count

CLI-only Tasks is an awareness count of enabled Scheduler rows explicitly marked cli_exclusive=1 with a known next execution.

Why the count is separate

The QCTNH wake-up transport is Joomla WebCron. CLI-exclusive work cannot be correctly represented as WebCron backlog, so QCTNH excludes it from Due Tasks/Next Eligible Task and displays the count separately.

What a nonzero value means

A nonzero CLI-only count is not a QCTNH error. It tells you that the site has scheduled work that requires a different execution path. Ensure those tasks are covered by Joomla CLI/server cron as appropriate.

Time and lock context

Understanding the CLI-only Tasks Count depends on current scheduler timestamps and Joomla’s timeout-derived lock threshold. A lock is not classified only by whether it exists; QCTNH compares its age with the Scheduler timeout (with a safety minimum) to distinguish recent active work from a soft/stale condition.

This is why changing clocks, restoring an older database, or interrupting a long-running task can make health look surprising until you inspect the underlying timestamps and process state.

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.