◆ Salesforce

Troubleshoot Query Plan in Developer Console

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 taskRun a query plan for the SOQL query 'SELECT Id, Name FROM Account WHERE CreatedDate =…+
Run a query plan for the SOQL query 'SELECT Id, Name FROM Account WHERE CreatedDate = LAST_N_DAYS:30' in the Developer Console. I need to see if it's using the 'CreatedDate' index.
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 seeing slow load times on the 'OpportunityList' page for users with many open…+
I'm seeing slow load times on the 'OpportunityList' page for users with many open opportunities. Before I deploy the next release, generate a query plan for the main SOQL query powering that list and highlight any parts of the query that could be optimized to speed up retrieval.
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 'ContactSearch' component, which uses a complex SOQL query, is timing out for users…+
The 'ContactSearch' component is timing out for some users, and the sales manager is frustrated.
The 'ContactSearch' component, which uses a complex SOQL query, is timing out for users searching for common names like 'Smith' or 'Jones', and the sales manager just called me upset because his team can't find critical contacts. I can't tell if it's a lack of indexing, a bad join, or just too many records. What's the most likely performance bottleneck based on a query plan, and what's the first thing I should try to improve it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI repeatedly write SOQL queries that work during development but then perform poorly in…+
My SOQL queries often perform poorly in production, leading to user complaints and system slowdowns.
I repeatedly write SOQL queries that work during development but then perform poorly in production, causing user complaints and system slowdowns. It feels like I'm always reacting to performance issues. What habit should I change in my query writing and testing process to proactively ensure my queries are efficient and scalable?
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.