Why a CLI-Only Scheduled Task Is Not Running Through QCTNH

A CLI-only Joomla Scheduled Task is deliberately excluded from QCTNH’s WebCron queue because the task declares that it must run through a CLI-capable scheduler context.

How QCTNH identifies it

Enabled task rows with cli_exclusive=1 and a next execution time are counted separately in the Dashboard’s CLI-only Tasks field. They are not included in Due Tasks/next eligible WebCron selection.

Why QCTNH does not override the flag

The task author may require CLI environment, resources, or semantics that are not safe in an HTTP request. Forcing it through WebCron would violate Joomla/task intent.

What to do

  1. Open Joomla Scheduled Tasks and identify the task type/owning extension.
  2. Confirm CLI-exclusive behavior is expected.
  3. Configure Joomla’s appropriate CLI/server-cron scheduler entry according to Joomla/hosting documentation.
  4. Use QCTNH for the web-runnable tasks it is designed to wake.

Avoid destructive shortcuts

The guidance for Why a CLI-Only Scheduled Task Is Not Running Through QCTNH does not require manually editing QCTNH identity, WebCron URL/key, scheduler locks, or next_execution in the database as a first response. QCTNH/Joomla already expose supported repair paths for registration, WebCron preparation, and task administration.

Direct database changes can break clone protection, hide credential drift, or allow overlapping tasks. Use them only as a separately planned recovery procedure with backups and clear source-level justification.

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.