---
schema_version: "1"
id: c850276e2074af60f4a508d7a166c1297616c4bc48e3ebd2319718566c7f4684
title: Flow Management
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-manager/flow-management.md
canonical_url: https://docs.mulesoft.com/runtime-manager/flow-management
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ebee36a3da3b10098caf672f958d2f1b75fd19feda55e79f48cb3a063b278e15
description: MuleSoft Documentation Site
latest: true
---
---
product: Runtime Manager
keywords: cloudhub, analytics, monitoring, insight, flow manager, flow management, start flow, stop flow
---

# Flow Management

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

[![logo hybrid active](/mulesoft/current/en-us/_/img/icons/hybrid-cloud.svg "Hybrid")Hybrid](deployment-strategies#hybrid-deployments)[ ![logo server active](/mulesoft/current/en-us/_/img/icons/server-cloud.svg "Anypoint Platform PCE")Private Cloud Edition](deployment-strategies#anypoint-platform-private-cloud-edition)

You can individually start and stop the specific flows within your deployed applications via the
Runtime Manager UI. All flows are active by default.

The flow management feature isn’t available for apps deployed to CloudHub and Anypoint Runtime
Fabric.

To act on flows, you must have **Manage Applications** permission on the desired applications.

## Start and Stop Flows

Individual flows can be set to active or inactive through the **Start** and **Stop** buttons.

Select one or more flows in your app, and click the **Start** or **Stop** button.

![flow management 983fd](/mulesoft/current/en-us/runtime-manager/_images/flow-management-983fd.png)

> [!NOTE] Starting a flow doesn’t imply triggering its endpoints, it just makes it active if
> previously set inactive.

## Set Flows to Unmanaged

In some cases, you can explicitly set up your applications to start and stop flows automatically
according to any criteria you want. In these cases, this behavior is carried out by logic in the
applications running inside Mule runtime itself, and Runtime Manager is unaware of the logic behind
these changes.

The default flow status for every application is unmanaged. This means that your flows freely
transition states between active and inactive according to the behavior set up in application logic
running in Mule runtime.

You can click **Start** or **Stop** for a flow in the **Flow Management** tab to override the
unmanaged status. In this case, Runtime Manager continually enforces the active or inactive state of
the flow, regardless of any changes Mule runime attempts. Click **Unmanage** to reset the flow
status to unmanaged at any time.

![flow management unmanage](/mulesoft/current/en-us/runtime-manager/_images/flow-management-unmanage.png)

## See Also

- [Flow Metrics](https://docs.mulesoft.com/runtime-manager/flow-metrics)

- [Manage Deployed Applications](https://docs.mulesoft.com/runtime-manager/managing-deployed-applications)

- [Manage Applications on Your Servers](https://docs.mulesoft.com/runtime-manager/managing-applications-on-your-own-servers)

- [Monitor Applications](https://docs.mulesoft.com/runtime-manager/monitoring)