Troubleshoot a Token-Backed QCDR Rule That Leaves the Original Text Unchanged

When a Token-backed Rule finds its text but leaves the original content unchanged, that can be QCDR's intended preservation behavior. The Rule will not replace a real match with an unresolved Token result.

Verify That the Rule Really Matches

Use private Preview / Rule Health when available. Confirm the Rule passes page, extension, audience, schedule, IP, and technical-condition checks, then verify the Find value and occurrence selection produce at least one eligible match.

If the Rule itself does not qualify, troubleshoot the Rule first. If Rule Health reaches Token readiness and reports a dependency problem, continue with the Token.

Both Processing Paths Matter

Rule Live Processing must be on for the live Rule. Token Live Processing must also be on for a Rule whose replacement mode depends on a Token. Turning Token processing off deliberately causes Token-dependent Rules to remain unapplied while direct-value Rules can continue.

Check the Replacement Token

• Confirm the referenced Token still exists and is Enabled.
• Check its required output tier and any tier inherited from nested dependencies.
• Verify its own targeting against the current request.
• For Joomla-data Tokens, confirm the source record is accessible to the current visitor.
• For PHP Tokens, confirm Max is currently effective and review Hide/Show error behavior.

Why QCDR Preserves the Original Match

The RuntimeEngine uses an internal unresolved value for dependencies that cannot be trusted. When a Rule's replacement resolves to that state, QCDR skips the replacement instead of inserting blank/broken content. The original matched text therefore remains intact.

This is different from a PHP Token that successfully returns an empty string. Successful empty output is a valid replacement and can intentionally remove the matched text.

Retest After the Dependency Is Fixed

Correct the Token state, entitlement, target, source data, or PHP problem, then rerun Preview on the same saved Rule and URL. Do not change the Find text merely because the original content was preserved; first confirm whether dependency readiness was the actual failing gate.

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.