QC Support Ticket Customer Reminders Scheduled Task
This article explains the 60-minute Pro reminder scan, Waiting for Customer eligibility, configured delay, and no-work/unavailable-plan success.
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
- Confirm the site currently has Pro / Max / All Access effective access before expecting the controls described here. A preserved configuration may still exist after downgrade even when the feature is locked.
- 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 |
|---|---|---|
| Customer Reminders | 60 minutes | Pro scan for eligible Waiting for Customer reminder messages. |
The routine scans for Pro-eligible tickets whose behavior is Waiting for Customer and whose configured reminder delay has elapsed. Tickets that are not eligible, or a site without the required effective plan, should produce a clean no-work result rather than an error.
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.