How To Debug Salesforce Flows?

Salesforce Flows have become an indispensable tool for Salesforce professionals, enabling them to automate complex business processes without writing a single line of code. However, like any other tool, Salesforce Flows can sometimes behave unexpectedly. This is where debugging comes into play. In this guide, we’ll delve deep into the various methods to debug Salesforce Flows, ensuring that your flows run seamlessly.

What You’ll Learn:

• Direct debugging using the Salesforce Flow Builder canvas.
• Handling errors through Flow Error Emails and understanding Failed Flow Responses.
• The innovative approach of debugging Record-Triggered Flows with reusable test cases.

 Let’s get started!

How to Debug Salesforce Flows

A. Debugging on Canvas

Canvas debugging is a popular method among Salesforce professionals. It provides a hands-on approach, allowing users to interact directly with the Flow Builder interface to identify and resolve issues. Here is the step-by-step process:

1. Accessing the Debug Mode: Once you’ve designed a flow and are confident about its structure, you’ll notice a ‘Debug’ button at the canvas’s top. This isn’t available for Platform Event Triggered flows but is present for most other types. Clicking on this button initiates the debugging process.
2. Setting the Entry Criteria: Before running the flow in debug mode, you need to specify certain entry criteria. This could be a Salesforce Record ID or any specific data that might initiate an action within the flow. The criteria you set largely depend on the flow’s design and purpose.
3. Monitoring the Flow’s Progress: After setting the entry criteria, you can execute the flow. As it progresses, you’ll receive detailed insights into how it’s processing variables and records. If you’re working with a Screen flow, you can navigate through each screen, inputting data to test the flow’s functionality before making it live.
4. Runtime Options for Comprehensive Debugging: The Flow Builder offers a plethora of runtime options tailored to the type of flow you’re debugging. Here’s a breakdown:

Record-Triggered Flow

• Run the flow as a different user.
• Set specific input conditions.
• Execute the flow in Rollback mode.
• Choose to skip start conditions.
• Decide between running the immediate path or the asynchronous path.

Screen Flow

• Execute as another user.
• Define input conditions.

Scheduled-Triggered Flow

• Use the Debug Pause Element.
• Operate in Rollback mode.

Auto-Launched Flow

• Run as a different user.
• Set input conditions.
• Utilize the Debug Pause Element.
• Engage in Rollback mode.

Omni-Channel Flow

• Execute as another user.
• Determine input conditions.
• Run in Rollback mode.

Understanding how to effectively debug on the Flow Builder canvas is crucial for anyone working with Salesforce flows. It ensures that your flows run smoothly, reduces errors, and enhances overall efficiency.

B. Debugging Salesforce Flows via Email Notifications

In the vast landscape of Salesforce flows, errors can occasionally emerge. A proactive approach to addressing these is through Flow Error Emails and Failed Flow Responses. Here’s the process:

1. Instantaneous Alerts: By default, Salesforce sends an email to the last person who edited the flow when an error occurs. This ensures immediate attention to the issue.
2. Expanding Notification Reach: Within Process Automation Settings, there’s an option to send error notifications to all Apex Exception Email recipients, broadening the alert system.
3. Deciphering the Error Email: Salesforce’s error email provides a runtime overview, pinpoints the problematic element, and offers clues like ‘Incorrect ID type’ or ‘Unexpected Null Value’, aiding swift troubleshooting.
4. Quick Access to the Problematic Flow: The email contains a direct link to the Flow Builder canvas of the erring flow, facilitating a faster fix.
5. Overview of Errors: Salesforce Setup features a ‘Paused and Failed Flow Interviews’ section, providing a list of all problematic flows and direct access for correction.

In essence, email notifications serve as an efficient tool for timely error detection and resolution in Salesforce flows.

C. Debugging Record-Triggered Flows with Reusable Test Cases

1. Introduction to Reusable Test Cases: Salesforce now offers the ability to craft reusable test cases for Record-Triggered flows. These test cases, reminiscent of Apex test cases, allow predefined data to be processed through the flow, determining its success. However, it’s essential to note that Delete context Record-Triggered flows currently don’t support this feature.

2. Creation Methods: There are two primary ways to generate these test cases:

Canvas Debugging: After constructing a flow, users can debug directly on the canvas. Upon successful completion of a Record-Triggered flow debug session, an option to ‘Convert to Test’ appears. This function captures the input values from the debug session, converting them into a reusable test case.

Manual Creation: Users can manually initiate test cases by selecting the ‘Test Cases’ button on the canvas. This method involves a structured three-step process:

• Test Details Configuration: Users specify the test case’s name, decide if it’s triggered on record creation or update, and choose between Immediate or Asynchronous contexts.
• Triggering Record Selection: Here, users determine the record that will initiate the flow. They can either select an existing record or specify criteria for the test.
• Assertion Settings: Users define conditions and custom failure messages for each assertion in the test case. During the test, all assertions are evaluated. If they all hold true, the test passes. Conversely, if even one fails, both the assertion and the test run are deemed unsuccessful. Any assertion failure during the test run will display the custom failure message in the test details.

These reusable test cases offer a structured and efficient approach to debugging Record-Triggered flows, ensuring optimal performance and reliability.

Conclusion

Debugging Salesforce Flows is an art that requires a combination of visual assessment, error detection, and test case creation. By mastering these techniques, Salesforce professionals can ensure their flows run seamlessly, enhancing overall system efficiency.

For those keen on diving deeper into Salesforce and enhancing their skills, saasguru offers a golden opportunity. Join our community on Slack to interact with seasoned professionals, share insights, and learn from real-world experiences. 

Moreover, don’t miss out on our online Salesforce bootcamps, where hands-on training meets real projects, ensuring a comprehensive learning experience.