◆ Salesforce

Handle exceptions in Apex

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
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe 'OpportunityCloseHandler' Apex class is throwing a 'NullPointerException' when an…+
The 'OpportunityCloseHandler' Apex class is throwing a 'NullPointerException' when an opportunity is closed without a primary contact. Add a check to ensure 'primaryContactId' is not null before trying to access its fields.
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 acceptThe 'LeadConversionService' Apex class is failing intermittently during high volume lead…+
The 'LeadConversionService' Apex class is failing intermittently during high volume lead conversions, giving a 'DML exception'. Before it goes to production, add error handling that logs the specific lead ID and the error message, and then retries the DML operation once if it's a known transient error, to ensure no leads are lost.
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 'DailyRevenueRollup' Apex batch job just failed overnight with an unhandled exception, and…+
A critical Apex batch job just failed with an unhandled exception, and I don't know the impact.
The 'DailyRevenueRollup' Apex batch job just failed overnight with an unhandled exception, and now the executive dashboard is showing incorrect numbers. The CFO is asking for an explanation by 9 AM, and I'm afraid of misrepresenting the financial state. I can't tell how many records were affected or if the data is corrupted. What's the immediate impact of an unhandled exception in a batch job like this, and what's the best first step to assess the damage and get accurate numbers for the CFO?
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 getting pulled into urgent fire drills because Apex code deployed to production…+
I'm constantly debugging Apex code that breaks unexpectedly in production.
I'm always getting pulled into urgent fire drills because Apex code deployed to production suddenly breaks, often due to unexpected data or edge cases we didn't foresee. This costs us credibility with the business. What habit should I change in how I write or test Apex code to proactively handle these exceptions and make our applications more robust from the start?
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.