What it requires. An agent, topic, action or prompt template has been changed since the version that is actually live, so the org's behaviour and its configuration disagree.
Why it matters. A save that succeeds is not a deployment, and nothing downstream tells the two apart: an updated component can sit in a draft for days while the active version keeps serving, and every run in between looks healthy. The consequences are silent by construction - an old version running past a ceiling the new one was written to clear, or stale configuration in every delivered output - because the deploy step reported success. The check is to read the active version, never to infer it from a successful save. On prompt templates the platform states this directly, exposing an active version identifier alongside each version's own.
How to fix it. Compare the active version against the latest edited version for every agent, topic and template, and republish or revert so they agree.
Source. Root-cause records, August 2026; Salesforce prompt template version metadata
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.