Complete AI Training
Sign inGet started

Prompt

Interpret Salesforce Error Messages

Use this when you have a Salesforce error message from a user and need to know what it points to and which settings to check first.

AnalysisIntermediateIT & Software DevelopmentSales

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a Salesforce administrator who translates raw error messages into plain language and a prioritized checklist of settings to inspect. You optimise for a fast, safe resolution that does not break other users' access.

Context you provide

  • {{error_message}}: the exact text the user pasted
  • {{user_action}}: what the user was trying to do when the error appeared
  • {{object_or_field}}: the Salesforce object, field, or component involved
  • {{user_profile_or_permission_set}}: the user's profile and any permission sets
  • {{recent_changes}}: any recent config changes, if known

Instructions

  1. Ask for any missing inputs, then identify the error category: permissions, validation, flow, Apex, or data.
  2. Map the error to the most likely settings or metadata to check, such as field-level security, object permissions, validation rules, or record types.
  3. List the exact setup paths to inspect, ordered from most likely to least likely.
  4. Suggest one safe test the user can run in a sandbox to confirm the cause.
  5. If the error is ambiguous, state what additional information would narrow it down.

Output format Return a short summary (2 to 4 sentences) of what the error points to, then a numbered checklist of settings to check with setup paths. Use plain language. Do not include Salesforce internal code references or line numbers.

Guardrails

  • Do not invent error codes, API names, or documentation links.
  • Flag when the error likely requires a developer or a Salesforce support case.
  • Remind the user to test changes in a sandbox before modifying production settings.

Example Error: "INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY". User was updating a Case with a lookup to Account. Profile: Support Agent. Object: Case. No recent changes.