--- canonical: https://amplience.com/developers/docs/workforce/flows/run/ title: Running flows description: Learn how to run Workforce Flows, view your flow library, track progress and manage automated tasks within your workflows. audience: Business User image: https://cdn.media.amplience.net/i/ampproduct/content-flows-library-with-enable-option?w=1200&h=630 image_width: 1200 image_height: 630 date_published: 2026-08-10 date_modified: 2026-08-10 --- # Running flows Once a flow has been created, you can **run** it to automate a process. As a flow runs, you can monitor its progress, view the actions being executed, and [review the outputs it produces](https://amplience.com/developers/docs/workforce/flows/review/). > **Info: Permissions for running flows** > Flows are stored with a hub, and to run them you will need the [Author](https://amplience.com/developers/docs/concepts/permissions/roles/#author) role or higher. More about [Workforce permissions](https://amplience.com/developers/docs/concepts/permissions/roles/#roles-and-workforce). To run a flow, launch it from your Flows library. ![Workforce with the Flows icon highlighted showing how to access Flows](https://cdn.media.amplience.net/i/ampproduct/content-flows-library-with-enable-option?w=1880&fmt=png 'Workforce with the Flows icon highlighted showing how to access Flows') Each flow is shown as a card with its name and description. The card also shows: - Whether the Flow can be run - this is controlled by Admin users, who [enable Flows](#enabling-flows-to-be-run) - How it runs (manually or automatically) - enabled Flows display a **Run** button on the card, that users can click to start the Flow. Learn more about [Triggers](https://amplience.com/developers/docs/workforce/flows/triggers/) Hover over a card to: - **Copy flow details:** Copies the flow label and ID to the clipboard (useful for developers using theGraphQL Management API) - **View runs:** Opens the Runs list filtered to that flow - **Duplicate flow:** Creates a copy of the flow in the current hub - **Edit flow:** Opens the flow in the editor - **Delete flow:** Prompts for confirmation, then deletes the flow and any associated runs and reviews As a flow runs, each action is shown in an action card so you can track progress. ![Workforce Flows with a flow run in progress](https://cdn.media.amplience.net/i/ampproduct/content-flows-run-in-progress?w=1880&fmt=png 'Workforce Flows with a flow run in progress') > **Note:** Running a flow is an asynchronous process that takes an indeterminate amount of time. ### Runs list All runs, whether in progress or completed, are shown in the **Runs** list. You can view more information about a run by clicking on it to show its [Run detail](#run-detail). **Note:** Run data is maintained for 90 days. ![Workforce Flows with runs listed in the Runs tab](https://cdn.media.amplience.net/i/ampproduct/content-flows-runs-list-1?w=1880&fmt=png 'Workforce Flows with runs listed in the Runs tab') ### Run detail Opening a run shows its detail, such as the flow actions and the order in which they were performed. Each action, is represented by a card including its name, status (in progress or complete), description and output. In the example below, the output of the **Trim Image** action is shown in a card. ![Workforce Flows with a run details window open](https://cdn.media.amplience.net/i/ampproduct/content-flows-runs-details-multiple-cards-2?w=1880&fmt=png 'Workforce Flows with a run details window open') ### Run statuses While running, a flow can have the following statuses: - **Queued** The run has been triggered, but is in a queue waiting to start - **In Progress** The run has started - **Paused** The run is waiting for a review task to be completed - **Complete** The run has finished. - **Aborted** - The run has been cancelled - **Expired** - The run timed out (reached the maximum duration of 90 days) - **Failed** - The run cannot continue due to an unrecoverable error, or too many repeated errors (too many retries) ## Enabling flows to be run Admin users control which Workforce Flows are allowed to run - giving them the flexibility to pause automations and prevent unintended runs. By default, flows are created as **Disabled**. In this state, they can only be run in **Test** mode by Admin users and are not available to non-admin users. To make a Flow available to other users, an Admin must set it to **Enabled**. This can be done from the Flows library or while building Flows. See [Building a flow in minutes](https://amplience.com/developers/docs/workforce/flows/getting-started/). ## Related pages [Get started in 5 minutes](https://amplience.com/developers/docs/workforce/flows/getting-started/) [Reviewing flow output](https://amplience.com/developers/docs/workforce/flows/review) [Example flows](https://amplience.com/developers/docs/workforce/flows/examples/) [Webhook triggers](https://amplience.com/developers/docs/workforce/flows/webhook-triggers/) [Developing extensions](https://amplience.com/developers/docs/workforce/flows/developing-extensions/)