Debug flows and save reusable test scenarios in one place with the new Flow Test Mode (beta) for record-triggered and autolaunched flows. Test flows in isolation with mock outputs for Action and Subflow elements. Generate flow test scenarios from the command line with headless Agentforce for Flow. Enter a static record ID to debug flows with specific records. Populate primitive and record collection inputs to test more scenarios.
- Test Flows in a Dedicated Test Mode (Beta)
Switch between building your flow and testing it in one place, and reuse saved test scenarios so you don't reenter inputs every time. Use Test Mode in Flow Builder to debug and save test scenarios in autolaunched and record-triggered flows. - Test Flows in Isolation with Mock Outputs for Action and Subflow Elements (Beta)
Test your autolaunched and record-triggered flows more reliably with mock outputs for Action and Subflow elements. Define consistent test data for external callouts and subflow responses without depending on live systems or external services. Mock outputs are available in autolaunched flows and record-triggered flows. - Generate Flow Test Scenarios with Agentforce for Flow
Skip the manual setup and let Agentforce for Flow Headless draft your test scenarios from a terminal, without opening Flow Builder. Use Agentforce for Flow Headless to create test scenarios for record-triggered, autolaunched, and Data Cloud-triggered flows without leaving your terminal environment. Through your connected terminal, you can generate comprehensive test scenarios for your flow, including success, fault, and edge-case paths. - Test Flows with Specific Records by Entering a Record ID
Enter a static 15-character or 18-character record ID directly in the Flow Builder debugger to debug flows with specific records. This option helps test flows that use objects with limited searchability, such as Cases or Campaign Members, without digging through lookup results. - Test Flows with Primitive Collection Inputs
Test different input values by populating primitive collections directly in the Flow Builder debugger. Previously you could only test single input values, not collections. Try various scenarios without editing your flow, reducing development time and improving test coverage. For example, if your screen flow or autolaunched flow accepts a text collection of IDs as an input variable, you can now populate that collection directly in the flow debugger.