Loading

Flow trigger error: 'The record couldn’t be saved because it failed to trigger a flow.'

Julkaisupäivä: Jun 19, 2026
Kuvaus

What Causes the 'Failed to Trigger a Flow' Error?

The error "The record couldn't be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301***. Contact your administrator for help" can appear when:

  • Saving a record in the Salesforce UI.
  • Running an Apex test class manually or via deployment.
  • Performing an insert or update through the API.

This error indicates that a Flow that is configured to run when the record is saved has encountered a problem. Use the debugging options below to identify the root cause.

Ratkaisu

Use the following options to identify the cause of the 'Failed to Trigger a Flow' error.

Option 1: Check Error Email

The creator of the Flow receives an error email with detailed step-by-step information and the error message. This is a great first step to determine whether the issue is data-related or implementation-related.

Option 2: Capture Debug Logs

Capture debug logs with the Workflow debug level set to FINEST. The debug log will often identify exactly which Flow element is failing and why.

Option 3: Use the Flow Debug Screen

Open the Flow in the Flow Designer and press Ctrl + Shift + M (Windows) or Command + Shift + M (Mac) to display the Request and Response details in the debug screen.

Option 4: Use Workbench REST Explorer

Use the Workbench REST Explorer to retrieve Flow metadata and identify the failing element:

  1. Get the version ID from the error message.
  2. Log in to Workbench.
  3. Go to Utilities → REST Explorer and perform a GET request.
  4. Add the following to the URI field (replace the ID with your Flow version ID): /services/data/vXX.x/tooling/sobjects/flow/30124000000PcNDAA0 — use the latest API version in place of vXX.x.
  5. Click Execute.
  6. Open the attributes folder.
  7. Check the ProcessType field. A value of Flow indicates a normal Flow; a value of Workflow indicates a Process Builder flow. The MasterLabel field shows the name.
  8. Explore the Flow metadata tree to understand what each element does. This is especially useful for Process Builder flows, where error messages may reference auto-generated names like myRule1_1.

NOTE: Using DELETE in REST Explorer will permanently delete an inactive Flow. Use caution when working in REST Explorer.

Most Common Flow Error Messages

Knowledge-artikkelin numero

000382895

 
Ladataan
Salesforce Help | Article