Why QCUI Does Not Require Joomla Scheduled Tasks

Why QCUI Does Not Require Joomla Scheduled Tasks is a deliberate QCUI 1.0.03 behavior that protects administrator access, target-account safety, or the integrity of the one-time impersonation handoff.

Event-driven plugin

QCUI listens to Joomla system events and explicit POST actions. It injects UI during page rendering, issues/consumes tokens during user actions, and opportunistically cleans old token rows when issuing a new handoff.

No periodic work

There is no recurring remote check, queue processor, report sender, or maintenance routine that needs Joomla Scheduler. Therefore QCUI registers no Scheduled Task.

Troubleshooting implication

If impersonation is broken, looking for a missing QCUI Scheduled Task is the wrong diagnostic path. Focus on plugin state, permissions, target eligibility, tokens, sessions and assets.

Current-product boundary

Why QCUI Does Not Require Joomla Scheduled Tasks reflects QCUI 1.0.03 as released: one System plugin, one token-lifetime setting, explicit Super-User initiation, no Scheduled Tasks, and no licensing/entitlement layer. Keep that boundary in mind when comparing older notes or assumptions from other QuantaCade products.

Current-product boundary

Why QCUI Does Not Require Joomla Scheduled Tasks reflects QCUI 1.0.03 as released: one System plugin, one token-lifetime setting, explicit Super-User initiation, no Scheduled Tasks, and no licensing/entitlement layer. Keep that boundary in mind when comparing older notes or assumptions from other QuantaCade products.

Community Discussion

Want to compare support workflows, share practical tips, or discuss how you use this QCUI feature? Visit the QC User Impersonation Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.