# Accessing process flow versions

## Introduction

All versions associated with a process flow can be accessed via the `versions` panel in [process flow settings](/product-documentation/process-flows/building-process-flows/process-flow-settings.md). From here, you can view summary details for each version and, if required, switch to a given version on the canvas.

## The steps

{% stepper %}
{% step %}
**Log in to the Patchworks**&#x20;

If you haven't done so already, log in to the [Patchworks dashboard](https://app.wearepatchworks.com/login).
{% endstep %}

{% step %}
**Access process flows**

Select `process flows` ➤ `process flows` from the left-hand navigation menu:

<div align="left"><figure><img src="/files/IJKVqwl8KqwJmD9WFA8k" alt="" width="238"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Access process flow settings**

Select `flow settings` from the actions bar - for example:

<div align="left"><figure><img src="/files/ap0rrflF0BF5lCiQUqn9" alt="" width="324"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Scroll to versions**

Scroll down to the `versions` panel, where all existing versions of the process flow are listed:

<figure><img src="/files/NB7scJxDDpQ9eoA4MtUw" alt=""><figcaption></figcaption></figure>

The version that's currently available to view and (if applicable) edit on the canvas is shown with an 'eye' icon in the selected column. To switch to a different version, click anywhere in the associated row - for example:

<div align="left"><figure><img src="/files/KT5Zyfe5MU2fCWIG290B" alt="" width="351"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

## Understanding the process flow versions panel

The versions panel is available in [process flow settings](/product-documentation/process-flows/building-process-flows/process-flow-settings.md) - for example:

<figure><img src="/files/DRewyttJPKJLJhCdpS6i" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Version details are different if you use virtual environments - in this case, please refer to [Reviewing version information for virtual environment process flows](/product-documentation/virtual-environments/implementing-virtual-environments/deploying-a-single-process-flow-to-a-virtual-environment/understanding-flow-versioning-for-virtual-environments/reviewing-version-information-for-virtual-environment-process-flows.md).
{% endhint %}

From here, you can see the following details for each *version*:

<table><thead><tr><th width="246.2109375">Heading</th><th>Summary</th></tr></thead><tbody><tr><td>#</td><td>The flow version number. The version number remains constant unless another version is deleted, in which case any remaining version numbers update accordingly.</td></tr><tr><td>ID</td><td>The unique identifier associated with a version. This identifier remains constant, even if the original version number changes as a consequence of another version being <a href="/pages/IPlGo1zifUs9zjWjwYeB">deleted</a>. <br><br>If you are using our API to work with virtual environments, you'll need this <code>id</code> to target the required flow version.</td></tr><tr><td>Selected</td><td>Indicates which version is currently displayed on the <a href="/pages/knwq5IXZdfnXDkeThtCN">canvas</a>.</td></tr><tr><td>Created</td><td>The date and time (UTC) this version was created.</td></tr><tr><td>Updated</td><td>The date and time (UTC) this version was updated.</td></tr><tr><td>Status</td><td>The current status of this version. Each new version of a process flow starts as a <code>draft</code>, and increments the version number. The version then progresses through its own <a href="/pages/OgVW3ibKhwdcNKCbKOj5#version-types-summary">lifecycle</a> (where a <code>draft</code> can become <code>deployed</code> and a <code>deployed</code> version becomes <code>inactive</code> when superseded by another deployment.<br><br>Note that flow versioning works a little differently if you use virtual environments. In this case, please refer to <a href="/pages/JfIV5L8UTupZFmUOTxgL">Understanding flow versioning for virtual environments</a>.</td></tr><tr><td>...</td><td>Access <a href="#version-options">options to work with the selected version</a>.</td></tr></tbody></table>

### Version options

The ellipsis associated with each version provides access to the following options (availability varies, depending on the version status):

<table><thead><tr><th width="198.3359375">Option</th><th>Applicable from status...<select multiple><option value="NYQEX25HHYWG" label="draft" color="blue"></option><option value="YMhkJCk0rBUW" label="inactive" color="blue"></option><option value="r4OOuW1b4nN4" label="deployed" color="blue"></option></select></th><th>Summary</th></tr></thead><tbody><tr><td>Duplicate flow</td><td><span data-option="NYQEX25HHYWG">draft, </span><span data-option="r4OOuW1b4nN4">deployed, </span><span data-option="YMhkJCk0rBUW">inactive</span></td><td>Copy the selected flow version to a new process flow.</td></tr><tr><td>Copy to draft</td><td><span data-option="r4OOuW1b4nN4">deployed, </span><span data-option="YMhkJCk0rBUW">inactive</span></td><td>Overwrite the existing draft version with content from the selected flow version.</td></tr><tr><td>Upload to marktplace</td><td><span data-option="r4OOuW1b4nN4">deployed</span></td><td>Upload the selected version to your <a href="/pages/Yh6SKOPDHxyeAAMVa7BT">private marketplace</a> (only applicable if the <a href="/pages/5JzXXY339CKzG84bKWYR#about-the-partner-features-bolt-on">partner features bolt-on</a> is enabled for your company profile).</td></tr><tr><td>Delete</td><td><span data-option="YMhkJCk0rBUW">inactive</span></td><td>Deletes the selected version entirely.</td></tr></tbody></table>


---

# 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/process-flows/building-process-flows/process-flow-versioning/accessing-process-flow-versions.md?ask=<question>
```

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.
