◆ Salesforce

Mass delete flow and flow versions

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 taskDelete all versions of the 'New Client Onboarding' flow, and then delete the flow itself. Make…+
Delete all versions of the 'New Client Onboarding' flow, and then delete the flow itself. Make sure to clear the recycle bin afterward.
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 delete these old 'Lead Nurturing' flows, can you tell me which ones are still…+
Before I delete these old 'Lead Nurturing' flows, can you tell me which ones are still referenced by active custom buttons or Apex triggers? I want to avoid breaking anything important for the sales team.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to clean up old 'Opportunity Follow-up' flows, but when I try to delete them, I get…+
I just tried to delete a flow, and it failed with a vague error about dependencies.
I'm trying to clean up old 'Opportunity Follow-up' flows, but when I try to delete them, I get a 'cannot delete active version' error, even after deactivating. I'm worried I'll accidentally delete something critical that a sales rep is relying on. What's the real dependency, and what's the safest way to get rid of these without impacting anyone's pipeline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm always finding myself with dozens of inactive, outdated flows that make it hard to manage…+
I keep accumulating old, inactive flows that clutter the system and make it hard to find current ones.
I'm always finding myself with dozens of inactive, outdated flows that make it hard to manage the system and slow down my work. It feels like I'm constantly wading through old versions. What's a better habit for managing flow lifecycles so I'm not always playing catch-up and risking system performance?
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.