QC Support Ticket Entitlement Revalidation Scheduled Task
This article explains the 60-minute security-canonical task, task-integrity requirements, bounded outage grace, and Basic fallback when structurally unhealthy.
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.
Current routine
| Task | Canonical/default cadence | What a run does |
|---|---|---|
| Entitlement Revalidation | 60 minutes | Security-canonical Authorized-Domain entitlement refresh. |
Security boundary
- A missing, disabled, duplicate, structurally invalid or slower-than-required canonical entitlement task cannot be treated as healthy paid-state security.
- QCST falls above-Basic Effective access back when task integrity is structurally unhealthy rather than preserving stale premium use forever.
- Temporary service/transport continuity is bounded and cannot outlive a known paid/Preview expiration.
- The task revalidates existing entitlement; it does not silently start an untouched Max Preview.
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.