--- schema_version: "1" id: 91939811385bb0a665864299a00cb4eae0a1098fb13bef6fc27acd27580663d4 title: Troubleshooting Flow Run Time Errors collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_troubleshoot_email.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_email.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 71b0ae1f8ffafb483a70fb1e29330e7f59f42cb2c235a1e39408021086c4c4b3 description: 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. products: - Flow Builder - Salesforce Platform release: "264" --- # 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 ran, and a link to view the failed flow in Flow Builder. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_example.png) 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](https://help.salesforce.com/s/articleView?id=platform.flow_test_debug.htm&release=264.0.0&type=5 "For flows that don't use Test Mode, use the Debug option to test or troubleshoot the flow. Review step-by-step details of how the flow runs and the path it takes."). - 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. When a flow run encounters an error and takes a fault path, the flow runs the elements in the fault path to handle the error. In some cases, an error email can also be sent. - 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) 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](https://help.salesforce.com/s/articleView?id=platform.automate_flow_troubleshoot_required_field_missing.htm&release=264.0.0&type=5)** 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](https://help.salesforce.com/s/articleView?id=platform.automate_flow_troubleshoot_cpu_limit.htm&release=264.0.0&type=5)** 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](https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_url.htm&release=264.0.0&type=5)** 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](https://help.salesforce.com/s/articleView?id=platform.automate_flow_troubleshoot_retries.htm&release=264.0.0&type=5)** 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 - [Considerations for Flow Error Emails](https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_email_limitations.htm&release=264.0.0&type=5 "Review these considerations for the email sent to the admin or Apex exception email recipients regarding flow interview errors and Screen and Subflow elements.") - [Customize What Happens When a Flow Fails](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault.htm&release=264.0.0&type=5 "Learn how fault paths customize what happens when a flow fails. Choose how to notify admins, guide users, and take a follow-up action.") - [Flow Builder Debugger Considerations](https://help.salesforce.com/s/articleView?id=platform.flow_considerations_troubleshooting.htm&release=264.0.0&type=5 "Use these considerations when you debug a flow in Flow Builder.") - [What Happens When an Apex Exception Occurs?](https://help.salesforce.com/s/articleView?id=platform.code_apex_exceptions.htm&language=en_US) - [Select Flow and Process Error Email Recipients](https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_error_email.htm&release=264.0.0&type=5 "When a process or flow interview fails, a detailed email is sent to the admin who last modified the process or flow. However, sometimes the admin isn’t the best person to act on the details of what ran and what went wrong. In that case, you can send error emails to the Apex exception email recipients.") - [Send Alerts When a Screen Flow Fails](https://help.salesforce.com/s/articleView?id=platform.process_troubleshoot_error_event.htm&release=264.0.0&type=5 "To save time troubleshooting screen flows that fail, subscribe to the Flow Execution Error Event platform event. When a flow interview fails, Salesforce publishes a platform event message. In Process Builder, you can subscribe to the platform event and perform actions, such as posting to Chatter or sending custom notifications.")