◆ Salesforce

Deploy record-triggered flow with error message

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskDeploy the 'Opportunity_Closed_Lost_Reason' record-triggered flow to production by Tuesday,…+
Deploy the 'Opportunity_Closed_Lost_Reason' record-triggered flow to production by Tuesday, ensuring the error message 'Please select a valid reason' appears if the 'Lost Reason' field is blank.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I deploy the 'Opportunity_Closed_Lost_Reason' flow, make sure the error message is clear…+
Before I deploy the 'Opportunity_Closed_Lost_Reason' flow, make sure the error message is clear and helpful to sales reps. It needs to guide them to the right field without making them feel like they're being scolded.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'Opportunity_Closed_Lost_Reason' flow just went live, and reps are complaining about a…+
The new 'Opportunity_Closed_Lost_Reason' flow is live, but reps are complaining about a generic error message when they try to save.
The 'Opportunity_Closed_Lost_Reason' flow just went live, and reps are complaining about a generic 'An error occurred' message instead of 'Please select a valid reason' when they try to save a lost opportunity without a reason. I'm afraid they'll ignore it. What's the most likely cause for the custom error message not showing, and how can I quickly fix it without rolling back the entire deployment?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently struggle with deploying flows that include custom error messages; they often…+
I consistently struggle with deploying flows that include custom error messages, leading to user frustration.
I consistently struggle with deploying flows that include custom error messages; they often don't display correctly, leading to user frustration and support tickets. What habit should I change in my testing or deployment process to ensure custom error messages always work as intended before they hit production?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.