# Enabling & disabling a process flow (without virtual enviroments)

## Introduction

If you've [built](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows) and [deployed](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/flow-deployment/deploying-a-process-flow-without-virtual-environments) a new process flow, you must enable the flow so it runs automatically based on defined [trigger settings](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape).

If you need to pause a process flow from running automatically (for example, to troubleshoot an issue with associated systems), you can `disable` it at any time, then [re-enable when you're read](https://doc.wearepatchworks.com/product-documentation/virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/disabling-or-enabling-a-process-flow-deployment-for-a-virtual-environment)y.   

Availability of `enable` and `disable` options depends on the current state of the selected flow deployment. If a flow deployment is `enabled`, then a `disable` option is available. If the selected flow deployment is `disabled`, an `enable` option is shown.

{% hint style="warning" %}
If you use [virtual environments](https://doc.wearepatchworks.com/product-documentation/virtual-environments), different instructions apply - please refer to [Disabling & Enabling a process flow deployment for a virtual environment](https://doc.wearepatchworks.com/product-documentation/virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/disabling-or-enabling-a-process-flow-deployment-for-a-virtual-environment).
{% endhint %}

## The steps

{% stepper %}
{% step %}
**Access version details for the required process flow** 

Open [settings](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-settings) for your process flow and scroll down to the `versions` panel.

{% hint style="info" %}
For detailed instructions, please refer to [Accessing process flow versions](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-versioning/accessing-process-flow-versions).
{% endhint %}
{% endstep %}

{% step %}
**Check the enabled/disabled status**

Check how the `enabled` toggle option (near the top of the settings panel). For example:

<figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FXv2YhOPghK1eLx4OUKWK%2Fdeploy%20-%20check%20enabled.png?alt=media&#x26;token=7f8a989d-38bb-45bc-924c-ddf64d350790" alt=""><figcaption></figcaption></figure>

Set this option as required, bearing in mind:

* If this option is toggled `off`, the flow will NOT run according to any defined [trigger settings](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape) - it only runs if you choose to do so [manually](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/initialising-a-process-flow-manually) (useful if you are testing a flow).  &#x20;
* If this option is toggled `on`, the flow will run according to any defined [trigger settings](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape) immediately. &#x20;
  {% endstep %}
  {% endstepper %}