---
schema_version: "1"
id: 53e6c16f8b81556cd9c281e5a29342cd6f5f0785d59c6b99990f02aa52a1748e
title: Test Flows in Isolation with Mock Outputs for Action and Subflow Elements (Beta)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_automate_flow_test_mock_output.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_test_mock_output.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1fadb28d0d917b2bb4318d901f2bc77529484821894a5cda36aba4935a3e5d9b
description: 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.
products:
  - Cross Cloud
release: "264"
---
# 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.

**Where:** This change applies to Lightning Experience in Professional, Enterprise, Performance, Unlimited, and Developer editions.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-264-0-0-production-enus/550ba85b-db1a-4608-9cd4-9a65ec96e1fa/images/icon_note.png)

Note This feature is a pilot or beta service that is subject to the Beta Services Terms at [Agreements - Salesforce.com](https://www.salesforce.com/company/legal/agreements/) or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the [Product Terms Directory](https://ptd.salesforce.com/). Use of this pilot or beta service is at the Customer's sole discretion.

**Why:** Previously, testing flows with Action elements that make external callouts or include Subflow elements required live connections to external systems or complete subflow execution, which made testing unpredictable when external services were unavailable or returned inconsistent data.

Mock outputs let you define what data Action and Subflow elements return during test runs, so scenarios validate flow logic, not external dependencies. When you mock a callout Action element, the flow skips the actual HTTP request and uses your predefined response. When you mock a Subflow element, the flow skips the referenced flow's execution and uses the mock output you specify.

Mock outputs are particularly valuable for testing:

- Action elements with HTTP callouts to external APIs that are rate-limited or unavailable
- Action elements that invoke Apex methods with complex dependencies
- Flows that include Subflow elements, without executing the referenced flows
- Fault paths that are difficult to trigger with live data

**How:** From Setup, in Quick Find, enter Process, and then select **Process Automation Settings**. Select **Flow Test Mode (Beta)**.

From the Flow Builder canvas, select **Test** to open Test Mode. Click the Action element or Subflow element that you want to mock. In the element's properties panel, click **Scenario Output**. Click **Use Mock Output** to enable mock output for this element.

![Action element properties panel in Test Mode, with the Scenario Output tab selected and an output field showing a JSON value.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-264-0-0-production-enus/550ba85b-db1a-4608-9cd4-9a65ec96e1fa/salesforce_release_notes/images/automate/264_rn_automate_flow_test_mock_output.png)

Define the mock output data for each output or copy the output values from a previous debug run in the debug history. Save your test scenario and run the test scenario. The flow uses your mock output instead of executing the Action element or Subflow element.