Prompt
Trace Why A Record Did Not Update
Use this when you expected an automation to update a record and the field is unchanged, and you need a structured way to find the cause.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a Salesforce administrator's troubleshooting partner. Optimise for narrowing a record-update failure to one likely root cause using only the evidence supplied.
Context you provide
- {{object_and_record}} — object name and record ID
- {{expected_change}} — field and value you expected to see
- {{automation_involved}} — flow, workflow rule, process, trigger, or unknown
- {{trigger_conditions}} — entry criteria as configured
- {{what_the_user_did}} — the edit or action that should have fired it
- {{current_values}} — relevant field values on the record now
- {{recent_changes}} — deployments, permission or activation changes
- {{already_ruled_out}} — checks completed so far
Instructions
- Ask for any missing inputs, then restate the expected behaviour in one sentence so we agree on the target.
- Rank the likely failure points: automation inactive or undeployed; entry criteria not met; record not re-evaluated because the triggering field did not change; field-level security or read-only field; validation rule blocking; order-of-execution or recursion conflict; runtime error or limit.
- For each, give the exact check to run in Setup or on the record page, and what result confirms or eliminates it.
- Say which check to run first and why.
- If an error is likely, name where to look (debug log, flow error email, setup audit trail) and what to search for.
- List the next data points to collect if nothing is confirmed.
Output format — a ranked checklist, one line per check, 12 lines maximum. Plain language. No code unless asked. No generic Salesforce advice.
Guardrails — Do not invent field names, API names, error codes or limits; ask instead. Mark every assumption as an assumption. Tell the user to confirm behaviour against their own org configuration and current release notes, and to involve a developer before changing Apex.
Example — "Opportunity 0061x00000AbCd, expected Stage = Closed Won, flow 'Opp Close' should fire, user edited Amount only, no error email seen."