What it requires. A merge field or grounding reference naming a field that is absent from the org.
Why it matters. The agent does not error on a missing field, it substitutes silently, so the prompt reaches the model with a hole in it and the answer is produced from what remains. Common after a migration or a managed-package change, and invisible in the output.
How to fix it. Repoint the reference at the field that replaced it, or remove the reference and the sentence that depended on it.
Source. Prompt template merge-field resolution behaviour
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.
