# Viewing flow deployments ## Introduction The `flow deployments` page lists all flow deployments (current and historic) across all your virtual environments, and also deployments made to `no environment`. For example:

Every deployment completed, irrespective of the deployment mechanism (i.e. deployed [individually](/product-documentation/virtual-environments/implementing-virtual-environments/deploying-a-single-process-flow-to-a-virtual-environment.md) or via a [package](/product-documentation/virtual-environments/virtual-environment-packages/managing-packages/deploying-a-package.md)), is listed. {% hint style="info" %} If a flow deployment is [deleted](/product-documentation/virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/deleting-a-process-flow-deployment-from-a-virtual-environment.md) from the associated virtual environment, the corresponding entry is removed from this list. Otherwise, deployments remain for all time. {% endhint %} ## Accessing the flow deployments page To access the `flow deployments` page, select `virtual environments` ➤ `deployments` from the left-hand navigation menu:

## Understanding the flow deployments page By default, flow deployments are listed in chronological order by deployment date/time, with the most recent deployments first. ## Working with flow deployments You can use [search and filter options](#search-and-filter-options) to refine the list, and you can use [actions](#flow-deployment-actions) to perform given tasks. Each entry is listed under a series of headings - for example:

These headings are summarised below:

Heading	Summary	Sort & filter?
Flow	The process flow name, displayed as a hyperlink (click the link to access the associated flow). If a deployment is associated with a flow version that has been subsequently deleted, the name will include a `deleted` marker.	can be sorted
Version	The process flow version that was deployed.	can be sorted
Package	If the deployment was made via a package, the package name is displayed as a hyperlink (click the link to access the associated package).	can be filtered
Virtual environments	The name of the target virtual environment (if applicable).	can be filtered
Deployed at	The date and time that this flow version was last deployed to the associated virtual environment. Typically, this won't change. However, if you were to deploy a flow version, then delete that deployment and subsequently re-deploy the same version to the same virtual environment, this value would be updated.	can be sorted
Enabled at	The date and time that the deployment was last enabled. When a process flow is deployed, it is enabled automatically, so typically this date/time is the same as the `deployed at` date/time. However, if you were to deploy a flow version, then disable that deployment and subsequently re-enable it, this value would be updated.	can be sorted
Enabled by	The username of the person who last enabled this deployment. Typically, this will be the same as the `deployed by` value. However, if you were to disable a deployment and subsequently it is re-enabled by a different user, this value would be updated.	n/a
...	Access actions that can be taken with the selected flow deployment.	n/a

### Search & filter options Use the `search` field at the top of the page to search by any part of a process flow name. For example:

You can also filter the list by `package` and/or `virtual environment`, using filter options associated with these columns. For example:

Note that: * Any virtual environments with at least one flow deployment (irrespective of whether those deployments are enabled or disabled) will be available for selection. * Any packages deployed at least once will be available for selection. ### Flow deployment actions The ellipsis associated with each deployment provides access to the following actions:

Option Summary

Disable / Enable

Option	Summary
Disable / Enable	Availability depends on whether the selected deployment is currently enabled or disabled, so you set the reverse state. Note that: If a deployment is `enabled`, it will run in the associated virtual environment. If a deployment is `disabled`, it will NOT run in the associated virtual environment.
Delete	Delete the selected deployment. This removes the flow version from the associated virtual environment and sets the status to `inactive`.

Availability depends on whether the selected deployment is currently enabled or disabled, so you set the reverse state. Note that:

If a deployment is enabled, it will run in the associated virtual environment.
If a deployment is disabled, it will NOT run in the associated virtual environment.

Delete Delete the selected deployment. This removes the flow version from the associated virtual environment and sets the status to inactive.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://doc.wearepatchworks.com/product-documentation/virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/viewing-flow-deployments.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.