Understand QCDR Target Fingerprints and Drift Warnings

A QCDR Target Fingerprint is advisory evidence captured when a Draft Rule is prepared from Max-tier Discovery. Rule Health can later compare that evidence with current rendered output and report whether the original target still appears exact, has probably changed, or can no longer be found.

Fingerprints do not replace the Rule search value and never authorize QCDR to silently retarget a Rule.

What a Fingerprint Can Describe

The stored version-1 fingerprint can include the selected HTML tag and identifying evidence such as text/selected value, element ID/attributes, route context, and the strongest component/module render region known at Discovery time. Route evidence can include component, view, content record ID, and menu context.

Exact Target Found

Rule Health reports a pass when the best current element is an exact fingerprint match, the saved render region is still present when one was recorded, and the relevant route context has not drifted. The message explicitly notes that QCDR did not need to retarget anything.

Likely Match After Drift

If the exact evidence changed but QCDR finds a sufficiently similar current element, Rule Health returns an informational warning. In 1.1.05 the candidate threshold is 35% fingerprint confidence. The message can also identify route changes or a missing original render region.

“Likely” is diagnostic evidence, not authority. QCDR does not adopt that candidate and does not rewrite the Rule's find value.

Target No Longer Found

When QCDR cannot establish a sufficiently similar candidate, the fingerprint row fails and can report route drift or a missing render region. The saved Rule itself remains unchanged.

Legacy or Invalid Fingerprints

If stored fingerprint JSON is invalid or not the current version-1 shape, Rule Health treats it as informational legacy evidence and ignores it for retargeting. Re-run Discovery and prepare a fresh Draft Rule if you want current drift evidence.

How Fingerprint Warnings Affect Live Result

The actual Rule search value remains authoritative. If the literal Rule still qualifies and matches but its saved fingerprint no longer identifies the original target, Rule Health can report the final Live result as informational rather than silently changing the Rule. That is a warning to verify whether the literal match is still the target you intended.

Safe Response to a Drift Warning

  1. Inspect the current page and the Rule Health fingerprint message.
  2. Open Discovery on the current frontend page if you need new evidence.
  3. Compare the likely/current element with the business intent of the Rule.
  4. Edit the Rule manually if the target genuinely changed.
  5. Save and Preview again before enabling the updated Rule.

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.