◆ Salesforce

Debug Apex code

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 taskI need to fix the Apex code in the 'OpportunityCloseHelper' class. The current version is…+
I need to fix the Apex code in the 'OpportunityCloseHelper' class. The current version is failing when a deal stage moves to 'Closed Won' for accounts in the 'Enterprise' segment, throwing a 'NullPointerException'. Can you identify the line causing this and suggest a fix so the deal can close successfully?
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 acceptI'm debugging the 'OpportunityCloseHelper' Apex class. The current error happens inconsistently…+
I'm debugging the 'OpportunityCloseHelper' Apex class. The current error happens inconsistently when closing deals, often related to custom fields not being populated. Before I dive into each scenario, can you help me refactor the error handling to be more robust and provide clearer messages to the sales reps, so they know exactly what's missing when it fails?
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 Apex code I just deployed to production is causing a 'DML Exception' when sales reps try to…+
The Apex code I just deployed to production is causing a 'DML Exception' when sales reps try to update any opportunity, and I'm getting frantic calls.
The Apex code I just deployed to production is causing a 'DML Exception' when sales reps try to update any opportunity, and I'm getting frantic calls. I thought I tested it thoroughly in sandbox, but now everyone's blocked. I'm afraid I missed a critical permission or an unhandled trigger condition that wasn't present in my test data. What's the most likely cause of a broad DML exception like this, and what's the fastest way to diagnose and roll back or hotfix it without further disrupting sales?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent Apex code fixes right after deployments, often for issues I…+
I keep getting pulled into urgent Apex code fixes right after deployments, often for issues I thought were covered.
I keep getting pulled into urgent Apex code fixes right after deployments, often for issues I thought were covered. It's eating into my development time and eroding trust with the sales team. The recurring pattern is that my sandbox testing doesn't always catch edge cases that appear in production. What habit can I change in my testing or deployment process to catch these critical issues before they impact the business, so I stop having to reactively put out fires?
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.