Keep QCDR Scheduled Entitlement Checks Healthy on Low-Traffic Sites

A correct Entitlement Revalidation task still needs Joomla's Scheduled Tasks runner to wake up and execute it. On a very quiet site, the task definition can be healthy while Last execution drifts behind because normal traffic does not trigger Joomla often enough.

Separate Task Integrity from Task Execution

QCDR's Status card verifies the task plugin, one published canonical task, and an hourly-or-faster schedule. It also reports Last execution, Last exit code, and Next execution.

If the structure is wrong, use QCDR's repair process. If the structure is correct but execution is late, investigate the Joomla scheduler runner/wake-up path instead of repeatedly recreating the task.

Check the Joomla Scheduled Task

  1. Open QCDR → Status → Entitlement Automation Integrity.
  2. Confirm one published canonical task and a cadence of 60 minutes or faster.
  3. Click Open Scheduled Tasks.
  4. Review Last execution, Next execution, failures, and the task's Joomla execution history.

A successful definition with an overdue Next execution is a scheduler-running problem, not a reason to create a second Entitlement Revalidation task.

Use a Reliable Joomla Wake-Up Strategy

For low-traffic production sites, configure a supported Joomla Scheduled Tasks execution method that runs independently enough for your traffic pattern. A server cron or another Joomla-native scheduler wake-up strategy can keep the Joomla scheduler moving even when visitors are sparse.

QCDR also displays a recommendation for QC Task Nudge & Health, which can help nudge Joomla Scheduled Tasks and provide scheduler-health visibility. It is a companion tool; Joomla Scheduled Tasks remain the authority for the QCDR task itself.

Do Not Work Around a Stalled Runner by Duplicating Tasks

Creating extra QCDR entitlement tasks makes integrity worse: QCDR expects exactly one published canonical task. Likewise, changing the interval to more than 60 minutes causes an immediate structural entitlement problem.

Verify Paid Entitlement After Scheduler Repair

After the runner is reliable, confirm a successful recent execution and healthy integrity card. If QCDR previously fell back to Basic, use Refresh Entitlement or allow the next successful task run to rebuild the current entitlement.

Community Discussion

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