Loading
Salesforce now sends email only from verified domains. Read More
Automate Your Business Processes
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Troubleshooting Flow Run Time Errors

            You are here:

            1. Salesforce Help
            2. Docs
            3. Automate Your Business Processes

            Troubleshooting Flow Run Time Errors

            Learn how to troubleshoot and resolve flow errors and unexpected behavior in your flows that occur after activation. Interpret error emails, and use best practices to identify and resolve issues quickly.

            Understanding Flow Error Emails

            If a flow run fails, Salesforce sends an email to either the admin who last modified the associated flow or the Apex exception email recipients. The email includes the error message, details about each flow element that the flow executed, and a link to view the failed flow in Flow Builder.

            Note
            Note If the flow run fails at multiple elements, or if failures occur in a batch of flow interviews, the recipients receive either multiple emails or one email with an error message for each failure.
            • Error Message: Describes what went wrong. Look for keywords like "unhandled exception," "element failed," or specific validation errors.
            • Flow Name and Version: Identifies which flow and version failed.
            • Element Details: Shows which element in the flow caused the error. The element's API name or label is usually included.
            • Stack Trace: For advanced troubleshooting, the stack trace can help pinpoint the source of the error, especially for complex flows or Apex actions.
            Example
            Example

            Error: An error occurred at element Send_Email_to_Contact. Missing required input parameter: RecipientId.

            What it means: The flow couldn't send the email configured in the Send_Email_to_Contact element because there wasn't a value in the Recipient ID field.

            Tips for Troubleshooting Flow Errors

            • Start by reading the error email carefully. Identify the problem element and error message.
            • Open the flow in Flow Builder and locate the element mentioned in the email.
            • Use the debug feature in Flow Builder to run the flow with sample data and watch for failures in real time. In the flow error email, click Flow Error: Click here to debug the error in Flow Builder. Learn more about the debugger in Test or Troubleshoot Flows With the Flow Builder Debugger.
            • Check for missing or incorrect input values, especially for required fields or variables.
            • Review fault connectors and error handling paths to ensure they are set up correctly.
            • Test the flow as different users to check for permission or access issues.
            • For record-triggered flows, verify that the triggering record meets all entry criteria.

            Best Practices for Easier Troubleshooting

            • Add descriptive labels and API names to flow elements and resources to make error emails easier to interpret. For example, Get Records 1 isn't as helpful in an error email as Get Related Contacts.
            • Use fault connectors on critical elements to provide user-friendly error messages and alternate paths. If a flow run encounters an error and takes a fault path, the flow executes the elements in the fault path instead of sending an error email.
            • Send notifications for easier tracking and resolution.
            • Document common errors and solutions for your team.
            • After fixing an error, retest the flow using the Flow Builder debugger.
            • Advanced: Log errors to a custom object for more error details.
            Note
            Note To store more information about an interview when it’s saved as a Salesforce record, build a custom object that references the interview’s GUID. An interview is assigned an 18-character Salesforce ID only when it’s paused and saved as a Salesforce record. Each interview, whether in-flight or paused, has a GUID.
            • Troubleshoot REQUIRED_FIELD_MISSING Errors in Flows
              When a flow attempts to create or update a record without populating all required fields, you receive a REQUIRED_FIELD_MISSING error.
            • Troubleshoot APEX_CPU_TIME_LIMIT_EXCEEDED Errors in Flows
              When a transaction consumes too much CPU time, Salesforce throws an APEX_CPU_TIME_LIMIT_EXCEEDED error. Flows share this limit with every other automation in the same transaction, including Apex triggers.
            • Troubleshooting Flow URLs
              If you’re distributing a flow and the custom button, custom link, or a direct flow URL isn’t working as expected, verify the referenced flow. In addition, verify its variables if you’re passing values into a flow from the URL.
            • Troubleshooting Flow Retries
              Learn how a flow is run again after it failed to finish successfully. A flow retry is when a flow runs again to process records that failed to save successfully.

            See Also

             
            Loading
            Salesforce Help | Article