Repair the QCBM Entitlement Revalidation Scheduled Task
QCBM requires its Entitlement Revalidation automation for every entitlement above Basic. The canonical task must be backed by the QCBM task plugin, published exactly once, and scheduled to run at least every 60 minutes.
Use QCBM's built-in integrity repair instead of manually creating several scheduler rows. The repair knows which task identity is canonical and disables duplicates safely.
Recognize an Entitlement Task Problem
Open the QCBM Status tab and find Entitlement Automation Integrity. It reports the task plugin state, number of published canonical tasks, validation cadence, last execution, last exit code, and next execution.
QCBM flags a missing task, unpublished task, more than one enabled Entitlement Revalidation task, a cadence slower than hourly, a failed last exit code, or an overdue next execution.
Use Repair Entitlement Task as a Super User
- Sign in as a Joomla Super User.
- Open QC Backup Manager → Status.
- Read and record the current integrity warning.
- Select Repair Entitlement Task.
- Return to the integrity card and verify the task is structurally healthy.
Normal QCBM settings permission is not enough for this repair. The repair is restricted to a Super User because it can enable the task plugin and change Joomla Scheduled Task rows.
What the Repair Actually Changes
If the task plugin is installed and its files exist, repair enables it when necessary. If no Entitlement Revalidation row exists, QCBM creates the canonical task.
When candidate rows exist, QCBM keeps the lowest-ID row as canonical, restores the correct task type/title/publication/note, restores the hourly execution rules, and disables additional duplicate Entitlement Revalidation rows. If the saved next-execution value is missing/invalid, QCBM schedules a new near-term execution.
What the Repair Does Not Reconfigure
The Entitlement repair is scoped to QC Backup Manager Entitlement Revalidation. It does not repurpose the separate Scheduled Backups, Backup Continuation, or Retention Cleanup tasks or overwrite their independent jobs.
Do not delete those other QCBM tasks because you are repairing entitlement automation.
When the Built-In Repair Cannot Help
If the task plugin is not registered, its files are missing, or Joomla's Scheduled Tasks table is unavailable/incomplete, QCBM marks the repair as unavailable. Reinstall the current QCBM package to restore missing plugin files/registration, or repair the Joomla scheduler infrastructure before retrying.
A Healthy Structure Can Still Have a Runtime Warning
A task can be structurally healthy but still show Running with a warning because the most recent run returned a non-zero exit code or the next execution is badly overdue. In that case, recreating the task may not address the cause.
Use Open Scheduled Tasks to inspect Joomla execution. If the task is overdue, verify a Joomla scheduler runner is actually active. If the last execution failed, capture the exit code and QCBM entitlement message, then check network/entitlement conditions.
Verify Entitlement After Repair
Once the integrity card is healthy, use Refresh Entitlement. Confirm the correct Effective tier and Verification state return, and check that Next automatic check is populated.
Do not treat one manual refresh as a substitute for the hourly task. Leave the automation healthy so paid entitlement can continue to be revalidated normally.
Community Discussion
Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.