Troubleshoot Scheduled Tasks, Entitlement, or Update Problems

This article covers separate task integrity, Joomla scheduler/CRON, Authorized Domain verification, preview/access expiration, transport outages, update-site problems, and package permissions.

Where this fits in QC Support Ticket

Scheduled Task, entitlement and update warnings share the Status tab but have different causes. Separate task registration/execution health, Authorized-Domain validation results and Joomla update-site/package discovery before changing configuration.

Primary location: QC Support Ticket frontend and administrator interfaces, depending on the permission or failure being tested.

Before you begin

  • Open Joomla Scheduled Tasks and confirm the QCST task plugin is installed and enabled before changing task intervals or CRON.

Troubleshooting procedure

  1. Separate task integrity from task execution. QCST Status can report canonical entitlement-task structural problems, while Joomla Scheduled Tasks/CRON determine whether routines actually run.
  2. For entitlement, verify the Authorized Domain, Base/Effective tier, Preview/paid expiration and current verification message before changing local configuration.
  3. For a transport outage, do not assume indefinite premium continuity; QCST uses bounded grace and known expiration limits.
  4. For late tasks, confirm Lazy Scheduler traffic or server CRON. Inbound mail particularly needs reliable 5-minute execution.
  5. For updates, verify the QuantaCade update-site record/network/package permissions and current 1.0.42+ package rather than using obsolete license-key instructions.

Current-version note

This documentation is based on QC Support Ticket 1.0.42, the package currently deployed on the QuantaCade production site. The behavior described for Troubleshoot Scheduled Tasks, Entitlement, or Update Problems should be checked against the current screen labels before applying instructions to an older QCST release.

Verify the result

  • The expected QCST routine exists once, is Published at the intended cadence, and completes without a repeated error state.
  • Repeat the test with the least-privileged normal role affected by the feature; do not rely only on Super User behavior.

If it does not work as expected

  • If a due task does not run on a quiet site, verify server CRON rather than repeatedly changing the QCST interval.
  • For entitlement warnings, separate structural task health (missing/disabled/duplicate/slow) from temporary network/validation results.

Community Discussion

For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.