Use QCST Status to Check Scheduled Task Health

This article explains what healthy, missing, disabled, duplicate, invalid, overdue, or failed entitlement task states mean and where operational task execution is checked.

Where this fits in QC Support Ticket

QCST 1.0.42 installs five current Joomla Scheduled Task routines: Entitlement Revalidation, Email Delivery Retry, Customer Reminders, Inbound Mailboxes, and Scheduled Reports. Older SLA Automation and Webhook Delivery task types are retired and should not be recreated as current QCST routines.

Joomla Lazy Scheduler can run due tasks during site traffic, but a server CRON invoking Joomla Scheduled Tasks is the more predictable choice when inbound mail or other time-sensitive work must continue on quiet sites.

Primary location: Joomla Administrator → System → Scheduled Tasks, with QCST health summarized under QC Support Ticket → Status.

Before you begin

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

How to do it

  1. Open QC Support Ticket → Status.
  2. Review the canonical Entitlement Revalidation task: healthy publication, uniqueness/structure, cadence and recent result are security-sensitive.
  3. Treat missing, disabled, duplicate, invalid, overdue or repeatedly failed states as distinct problems rather than one generic “scheduler error.”
  4. Check the remaining operational routines in Joomla Scheduled Tasks for recent execution/result.
  5. If the site is quiet and runs only Lazy Scheduler, verify server CRON before blaming QCST for late inbound email or reports.

Important behavior and limits

  • QCST 1.0.42 has five current Scheduled Tasks. Older SLA Automation and Webhook Delivery task types are retired.
  • Lazy Scheduler depends on site traffic. Server CRON is preferable when inbound mail or other time-sensitive work must run predictably.

Verify the result

  • The expected QCST routine exists once, is Published at the intended cadence, and completes without a repeated error state.

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.