Operations · Practical investigation guide
Investigate failed Salesforce background jobs
A job status narrows the question. Use its time window, class and error details to decide which evidence to inspect next.
Open the async-job investigation →Follow the evidence
- Set a focused time window. Open the async-job investigation. Choose days, optionally an Apex class and status, and a suitable result limit. For failures, use status Failed.
- Run and export the query. Use the API indicated on the step. Keep all columns, including Status, ExtendedStatus and NumberOfErrors. Export every result page.
- Read the counts and limits. Import the results. Review job types, statuses and error counts. If the query limit was reached, narrow the time window or class before drawing broader conclusions.
- Follow the evidence. Use exported timestamps and class names to identify relevant logs or related operations. Coordinate any retry with the owner of the job; this investigation does not rerun it.
Try it first
Choose “Try fictional sample” to explore the layout without connecting to an org. The sample is illustrative and does not diagnose a real job.
Five-minute fictional walkthrough →What this does not establish
An empty export does not prove no jobs failed. A status or error count alone does not establish root cause, full business impact or whether a retry is safe.
Continue your investigation
Logging and trace-window checks · Choose another starting point
Work from authorised exports. Browser analysis stays in the current tab; downloaded reports remain on your device.