---
schema_version: "1"
id: 96e760e12ac826e88765e1362f98c6bdb94ac177cc92a6be9d495739bb901f34
title: Configuring and Managing Flows
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/composer-salesforce/ms_composer_flows.md
canonical_url: https://docs.mulesoft.com/composer-salesforce/ms_composer_flows
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5925587f3810d74ab97ef9fc69a33bbb04e813f319309cf8d563093aa6b4a758
description: MuleSoft Documentation Site
latest: true
---
---
product: Composer for Salesforce
---

# Configuring and Managing Flows

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

After you collect the information described in [the preparation checklist](https://docs.mulesoft.com/composer-salesforce/ms_composer_checklist),
you can then [build](https://docs.mulesoft.com/composer-salesforce/ms_composer_using_a_flow_and_creating_trigger),
[activate](https://docs.mulesoft.com/composer-salesforce/ms_composer_activation), and [monitor](https://docs.mulesoft.com/composer-salesforce/ms_composer_monitoring) your flows. Building a
flow involves creating a new flow or cloning an existing flow; adding and testing a trigger; adding
and testing each action to be performed by the flow, in the order that you want each action
performed; and finally testing the completed new flow before activating it.

[Test](https://docs.mulesoft.com/composer-salesforce/ms_composer_test_flow) each trigger and action as you add it to your flow.

## Flow Details Page

Access the **Flow Details** page to see details about your flow:

![The Flow Details page in MuleSoft Composer for Salesforce](/mulesoft/current/en-us/composer-salesforce/_images/images/flow-details-sf.png)

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>The name of the flow.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Details about the flow:<div><ol type="a"><li><p><strong>Created On</strong>: The date on which the flow was created in the time zone set in your browser.</p></li><li><p><strong>Flow ID</strong>: The ID of the flow.</p></li><li><p><strong>Flow Owner</strong>: The owner of the flow.</p></li><li><p><strong>Last Modified</strong>: The date on which the flow was last modified in the time zone set in your browser.</p></li><li><p><strong>Status</strong>: The status or the flow. The status can be either active or inactive.</p></li><li><p><strong>Last Triggered</strong>: The date on which the flow was most recently triggered. This field displays the last time the flow was triggered by either an Event poll or the Scheduler.</p></li></ol></div></td></tr><tr><td><i data-value="3"></i><b>3</b></td><td>The <strong>Run History</strong> of the flow. Composer stores up to 1000 records per flow and can include only the last two weeks of data. For example, for a flow that produces 10 records per day, you can see the Run History for the last two weeks of data (14 x 10 = 140 records). For a flow that produces 100 records per hour, you can see no more than 10 hours of the Run History. Triggering a flow via the Scheduler always creates an entry in the Run History. An entry in the Run History is only added by an Event trigger when a record is either created or updated and passes any filter condition.<div><ol type="a"><li><p><strong>Start Date</strong>: The date on which the flow started in the time zone set in your browser.</p></li><li><p><strong>End Date</strong>: The date on which the flow ended in the time zone set in your browser.</p></li><li><p><strong>Status</strong>: The status of the flow. The status can be either <code>SUCCESS</code> or <code>FAILED</code>.</p></li><li><p><strong>Reference ID</strong>: The ID of the record or execution that triggered the flow. For Event triggers, the value in this field is the corresponding <strong>Record ID</strong>. For events triggered by the Scheduler, a unique <strong>Execution ID</strong> value is created for the run instance.</p></li><li><p><strong>Error</strong>: If a flow fails, the error message for the failure appears.</p></li></ol></div></td></tr><tr><td><i data-value="4"></i><b>4</b></td><td>The flow actions. You can delete, clone, or view an active flow. Note that if the flow is inactive, you can edit the flow.</td></tr><tr><td><i data-value="5"></i><b>5</b></td><td>The <strong>Run History</strong> actions. You can refresh the <strong>Run History</strong> section or filter the section by specified criteria.</td></tr></tbody></table>

## 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/)