Troubleshoot QCFUM Scheduled Tasks, Automation, and Temporary Access

QCFUM uses two Joomla Scheduled Task responsibilities that should be diagnosed separately: mandatory Entitlement Revalidation and the Scheduled Automation runner. A problem with one does not automatically mean the other is configured incorrectly.

Temporary-access expiration is a security obligation. QCFUM runs that enforcement before optional commercial automation and can keep the automation task published when temporary-access records still need enforcement.

Check Entitlement Revalidation First

  1. Open QCFUM Status and review Entitlement Revalidation health.
  2. Confirm the QCFUM task plugin is installed and enabled.
  3. Confirm exactly one canonical Entitlement Revalidation task is published.
  4. Confirm its schedule runs at least once every 60 minutes. QCFUM repairs the canonical task back to an hourly schedule when repaired.
  5. Check last execution/exit code and whether QCFUM reports the task overdue. An overdue task means the Joomla scheduler runner itself must be verified.

Understand the Failure Effect

If Entitlement Revalidation is missing, unpublished, duplicated, disabled, scheduled too slowly, or otherwise structurally unhealthy, QCFUM keeps Effective access at Basic until the task is healthy. Repair of the canonical entitlement task is restricted to a Super User.

Check Scheduled Automation Separately

Commercial Scheduled Automation requires Pro+ and the main automation switch. Its native task is seeded hourly, but a valid administrator-selected cadence is preserved. When commercial automation is unavailable or switched off, QCFUM skips nudges, queue retry, cleanup, reminders, and summaries—but still calls temporary-access expiration first.

Verify Temporary-Access Enforcement

When temporary access expires, QCFUM normally blocks the Joomla user and records the expiration. If the Joomla user no longer exists, the tracking row is marked accordingly. If the target is a protected administrative account, QCFUM refuses to block it and records an expired_protected result instead.

Low-Traffic Sites Still Need a Runner

A correct task record and next-execution time are not proof that Joomla is actually invoking Scheduled Tasks. Use Joomla task history/last execution together with QCFUM Status. On quiet sites, configure a reliable Joomla scheduler runner or another Joomla-native nudge mechanism rather than increasing QCFUM task intervals.

Community Discussion

Want to compare Joomla user-management workflows, share practical QCFUM tips, or discuss how other administrators use this feature? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.