Troubleshoot QCDR Entitlement Revalidation and Scheduler Health

Missing/disabled/unpublished/duplicate/slow task, repair action, task-plugin presence, execution result, hourly cadence, low-traffic scheduler behavior, and Basic security fallback.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to All plans; administrator. Where older manuals or walkthrough wording differs from the current source or the accepted keyless-entitlement behavior, the current implementation takes precedence.

Before You Begin

Capture the exact affected URL, Rule/Token state, tier, and visible result before changing multiple settings.
Use Rule Health/Discovery evidence where available instead of guessing at origin or eligibility.
Never include license secrets, arbitrary PHP secrets, credentials, or private customer data in public support material.

Step-by-Step Workflow

Reproduce the issue on one known frontend URL and record the exact visible result.
Check QCDR version, Base/Effective tier, and Status/task health before changing content.
Check the relevant Rule/Token state and the matching Live Processing switch.
Review every applicable target gate in order: page, extension, audience, schedule, IP, conditions, dependencies, protected areas.
Use Rule Health, Preview, or Discovery evidence where your plan/permissions allow it.
Eliminate cache/CDN effects before concluding that QCDR did not process the request.
Change one setting at a time and retest so the actual cause remains identifiable.

Missing/disabled/unpublished/duplicate/slow task

QCDR 1.1.05 uses the current keyless Authorized-Domain entitlement model. Basic remains the fallback feature set, while paid Pro/Max and All Access are resolved from the normalized Authorized Domain rather than a customer-entered current license key. The one-time 30-Day Max Preview starts only when an authorized administrator explicitly selects Start 30-Day Max Preview; installation, navigation, Refresh Entitlement, frontend requests, and the Scheduled Task do not consume an untouched preview. Base tier and Effective tier remain separate so All Access or Preview can temporarily elevate capability without rewriting the underlying product state. Upgraded sites can still show a Legacy License Key, but clearing it is a compatibility cleanup action and must preserve Rules, Tokens, settings, preview history, and current Authorized-Domain state.

For Troubleshoot QCDR Entitlement Revalidation and Scheduler Health, evaluate this against the exact frontend request that matters. A saved QCDR item can be valid in Administrator yet remain inactive because a different eligibility gate, dependency, permission, cache layer, or runtime safety boundary correctly prevents transformation. Keeping those concerns separate makes both testing and later support much easier.

Repair action

Task-plugin presence

Execution result

Hourly cadence

How This Fits into QCDR

Troubleshooting should isolate one eligibility gate or runtime boundary at a time and preserve a known-good recovery path.

The safest operating pattern is to keep configuration narrow, use QCDR’s private diagnostics before broad activation when your tier permits them, and preserve Joomla Administrator as the recovery surface. Because QCDR changes the rendered response rather than source files, a correctly disabled or bypassed runtime path should expose the underlying Joomla output again without requiring a source-file rollback.

Verify the Result

Status shows the expected Base and Effective tiers for the normalized domain.
Entitlement Revalidation is healthy and hourly unless the article is specifically diagnosing that task.
Reload the real frontend request instead of relying only on the saved Administrator form.
Check Joomla/CDN cache effects if the result is request-specific.

Common Mistakes to Avoid

Ignoring timezone/DST or inventing syntax for the reserved Custom recurrence field.
Changing several gates at once during troubleshooting, which makes the actual cause difficult to identify.
Testing only while signed in as Super User when ordinary users/guests are the intended audience.
Skipping a recovery plan before enabling a site-wide HTML, JavaScript, protected-area, or PHP-backed change.

Troubleshooting

If nothing changes, confirm the package-owned System plugin is enabled, the relevant Live Processing switch is on, and the item is eligible for the current Effective tier.
If targeting appears wrong, inspect page/menu/URL, extension, audience, schedule, IP, technical conditions, and protected-region behavior as separate gates.
If a Token-backed Rule preserves the original match, troubleshoot the Token dependency/readiness before changing the Find value.
If behavior differs between browsers/users, clear or bypass relevant Joomla/full-page/CDN caches and compare request context.
If private Preview/Discovery fails, start a fresh authorized same-site session and confirm the Joomla ACL action as well as the product tier.

Operational Best Practice

Make runtime changes deliberately: use a narrow scope first, keep broad Rules Draft or Disabled until tested, preserve the independent Rule/Token emergency switches, and record the QCDR version plus the exact Rule/Token and affected URL when handing a problem to another administrator. For high-impact HTML, protected-region, JavaScript, dynamic-data, or PHP work, test representative anonymous and authenticated requests and review caching before expanding scope.

Community Discussion

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