◆ Salesforce

Handle DML errors in asynchronous flows

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 taskWhen the customer record updates, make sure the related order still processes even if the…+
When the customer record updates, make sure the related order still processes even if the update fails because of a lock.
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 the customer record update saves, check if the related order is actively being…+
Before the customer record update saves, check if the related order is actively being processed. If it is, queue the update to retry later so we don't block the order.
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 customer service rep just tried to update an account, but it failed because another process…+
Our customer service team is getting 'unable to lock row' errors when they update a customer account, but the related support case needs to be created right away.
The customer service rep just tried to update an account, but it failed because another process had it locked. Now the rep can't create the urgent support case. I'm afraid we'll miss critical follow-ups. What's causing these locks, and what's the fastest way to get the support case created without losing the account update?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe're frequently hitting 'unable to lock row' errors on customer accounts, especially when…+
We keep getting 'unable to lock row' errors when multiple things try to update the same record at once.
We're frequently hitting 'unable to lock row' errors on customer accounts, especially when sales and service are both active. This delays critical updates and frustrates the teams. What habit can we change in our automation to prevent these conflicts and ensure updates happen reliably?
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.