How QCTNH Treats CLI-Only Scheduled Tasks

QCTNH intentionally excludes CLI-only Scheduled Tasks from its WebCron due queue because Joomla marks those tasks as requiring CLI execution.

Current filter

Web-runnable calculations require cli_exclusive = 0. Enabled rows with cli_exclusive = 1 and a next execution time are counted separately as CLI-only Tasks.

What QCTNH will not do

It will not force a CLI-only task through WebCron, change that task’s transport requirement, or mark the task runnable merely to reduce an overdue count.

What to do for CLI-only work

Configure a suitable server cron/Joomla CLI runner for the workload and monitor that path independently. QCTNH can still support other web-runnable tasks on the same site.

Execution boundary

For How QCTNH Treats CLI-Only Scheduled Tasks, remember that one WebCron request is an execution opportunity, not a command to run a named task. QCTNH never sends a task ID to force selection. Joomla receives its normal System - Schedule Runner request, applies its queue/lock/recurrence rules, and returns the result of the work it chose.

This design is why QCTNH can work with Scheduled Tasks from many extensions without knowing their business logic. It also explains why a task-specific error belongs first to the owning extension even when QCTNH successfully delivered the WebCron request.

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.