---
schema_version: "1"
id: a0d8bddab44e7fb2d2aace0e60a711fd10a7fd67d04033d971f01c8baf20440c
title: Testing a Composer Flow
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/composer-salesforce/ms_composer_test_flow.md
canonical_url: https://docs.mulesoft.com/composer-salesforce/ms_composer_test_flow
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5e61b924086e29b489fa7f4e3c677dfd03405efa05621c19e1343d43720fd974
description: MuleSoft Documentation Site
latest: true
---
---
product: Composer for Salesforce
---

# Testing a Composer Flow

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

By testing as you build your flow, you can ensure that each step and each field mapping in your flow
is working as expected before activation. Frequent validation provides near real-time feedback about
the success of your flow and enables you to fix errors as you build.

Testing processes and tests a single record. You must activate your flow to process all of your
records.

When testing your flow, note the following:

- A trigger step is required.

- Testing automatically ends after ten minutes if not halted by an error or manually terminated.

- The entire flow is executed and tested.

When testing your flows:

- Build your flow in a sandbox environment to test your flow using inactive accounts.

- Test your flows with sample or dummy records.

- Consider limiting the number of records processed if your test times out.

> [!NOTE] When you test a flow with many steps, Composer keeps only a limited number of tracking
> notifications, so early steps can appear blank even though they ran. Only the display is affected.
> Your flow still runs and creates records. To confirm the results, check the records in the target
> system. Composer is designed for simple, lightweight automations. See
> [Known Issues and Limitations](#ms_composer_ms_release_notes_ki.adoc).

To test a flow:

1.  In Composer, in the flows list, click the flow you want to test and click **Edit**.

2.  Click **Test**.  
    Composer notifies you when the test is complete. The execution results from the test appear on
    the card.

> [!NOTE] If you need to contact Support for troubleshooting purposes, you can export your flow as a
> JSON file to share your flow by clicking the wrench icon and selecting **Export**.

## See Also

- [Mulesoft Composer for Salesforce: Overview](https://docs.mulesoft.com/composer-salesforce/ms_composer_overview)

- [MuleSoft Composer for Salesforce: Getting Started](https://docs.mulesoft.com/composer-salesforce/ms_composer_prerequisites)

- [Composer Connector Reference](https://docs.mulesoft.com/composer-salesforce/ms_composer_reference)

- [Knowledge Articles](https://help.salesforce.com/s/)