Recommended Free Tools
Start with the exact symptom and the flow type: use Flow Builder Debug for eligible flows, Test Mode for autolaunched and record-triggered flows, and debug logs to investigate a real record-triggered transaction. If an interview failed or paused, check Flow Monitor in the Automation app. A successful debug run alone does not prove a production transaction is fixed.
1. Capture the failure before changing the flow
Write down the exact error text, affected record and operation, approximate time, user or automated process, and the flow name and version if available. Distinguish among a failed interview, a paused interview, and a flow that appears not to have started; each points to a different investigation.
Reproduce the issue with one narrowly defined record operation if possible. Targeted reproduction makes it easier to identify the relevant log when Salesforce generates large debug logs. See Salesforce’s debug-log guidance.
2. Choose a diagnostic tool that matches the flow
| Situation | Start here | What it can show |
|---|---|---|
| Screen flow or another eligible flow during development | Flow Builder Debug | Step-by-step path and resource values. Review rollback options before running. |
| Autolaunched or record-triggered flow | Test Mode | Reusable test scenarios for the flow types Salesforce documents for Test Mode. |
| Record-triggered failure during an actual save | Debug Logs | The real transaction’s execution sequence, flow activity, element failure, and limit details. |
| Interview stopped or paused | Automation app, Monitor tab | Failed-interview details and debug view, or a resume control for paused interviews when resuming is appropriate. |
Salesforce documents the distinction between Debug and Test Mode. Check rollback settings before a debug run: a run without rollback can execute actions such as DML and Apex, and closing the run does not undo changes already committed.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
3. Read the runtime log for a real save failure
- In Setup, open Debug Logs and create or select a debug level.
- Set a trace flag for the user or automated context that will reproduce the failure.
- Reproduce the same record operation, then open the log for that run.
- Find the flow interview start and inspect the first relevant error or failure event. Follow the message to the element, field, action, or resource it names.
Salesforce’s general debug-log setup guidance recommends Workflow at Finer for flows. For the specific error “failed to trigger a flow,” Salesforce’s error-specific guidance recommends Workflow at FINEST. If Finer does not capture enough detail for that error, follow the specific guidance. Inspect limit-usage events when you suspect a governor limit.
4. Check these common failure messages
“The record couldn’t be saved because it failed to trigger a flow”
This means a flow configured to run when the record is saved encountered a problem. Start with the flow error email, then capture a debug log and reproduce the save using the error-specific Workflow detail above. If the message includes a flow version ID, Salesforce describes using Tooling API metadata to identify the flow and element in its support article. Use metadata inspection carefully; avoid destructive REST operations.
REQUIRED_FIELD_MISSING
The flow tried to create or update a record without supplying a required field. Check the field named in the error, the flow’s assignments, and whether every relevant path supplies a value. Also check both system-required fields and fields your organization requires. Salesforce explains this error in its required-field troubleshooting guidance.
5. If the flow appears not to start, check interviews and entry conditions
Open the Automation app and select the Monitor tab. Review failed and paused interviews; a failed interview’s details include its error and can open debug details. Resume a paused interview only when doing so is appropriate for the record and business process. See Salesforce’s Flow Monitor guidance.
Then inspect the flow configuration: confirm that the record meets the entry criteria and that the create or update operation matches the configured trigger. These checks help distinguish a flow that did not qualify to run from one that started and later failed.
6. Do not assume a failed interview will retry
Retry behavior depends on the flow type and failure context. Salesforce documents retries at fixed intervals of 15, 30, 60, and 120 minutes for specified scheduled-path and certain after-commit or wait-based flows. Immediate before-save and after-save paths do not use that time-based retry. Check the applicable flow type and error context in Salesforce’s flow retry guidance before waiting for another run.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.7. Verify the fix in a realistic, safe test
Use a sandbox where possible and test the real record operation. Record-triggered debugging runs in rollback mode and covers a narrower scope than a full transaction. Other triggered flows or processes can change runtime behavior, so a successful debug session is not, by itself, proof that the production problem is resolved. Salesforce recommends using a sandbox outside debug and actual logs to investigate those interactions in its debugging guidance.
- Exercise every decision outcome, including the default, boundary values, and unexpected values.
- Check fault paths and the permissions of the user or automated context that runs the flow.
- For issues involving other automation, reproduce the transaction outside Flow Builder Debug and inspect its runtime log.
Salesforce’s flow testing guidance covers Test Mode and test scenarios.
Best Value
8. Make the next failure easier to diagnose
Add fault paths to elements that can fail, then decide what each path should do: show a useful message, capture details, or route the error for review. A fault path handles errors from the element connected to it; it does not automatically handle every failure elsewhere in the flow. Configure error notifications with useful flow resource values so the owner or administrator receives enough context to investigate. Salesforce describes fault handling and error notifications in its fault-path guidance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
