> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/workflows/test-publish-and-version-workflows.md).

# Test, Publish, and Version Workflows

## Save and Review Findings

Select **Save workflow** while building. Saving can preserve an incomplete draft, so review the **Findings** menu before testing or publishing.

Common findings include:

* a required module setting is missing
* a module is not connected
* a template token has an invalid mapping
* a condition outcome has no rule or connection
* a file is unavailable or unsupported
* a workflow path does not end in a delivery

## Test a Workflow

1. Open the draft version you want to test.
2. Resolve workflow errors and save your changes.
3. Select **Test Run**.
4. Enter test values in the workflow form.
5. Start the test and review the executed path.
6. Open **Workflow runs** and select **Test runs** to inspect the result later.

Test runs are kept separate from live runs. If a workflow is inactive, activate it before testing.

## Publish a Workflow

Before publishing, confirm that:

* the form contains all required fields
* the selected form is published
* every selected template version is published
* template mappings are complete
* condition outcomes and connections are valid
* document and file modules have valid inputs
* every path ends in a configured delivery module
* the workflow has been saved and tested

Select **Publish** to make the draft the active workflow version. Publishing is stricter than saving and is blocked until publish findings are resolved.

## Start the Workflow

Open **Trigger Options** after configuring the workflow:

* Use **Form** to copy or open the hosted form link.
* Use **API** to view the request information for starting the workflow programmatically.
* Select whether the link targets the published workflow or the latest draft when that option is available.

Use the published workflow link for live submissions.

## Workflow Statuses

The Workflows list displays the lifecycle of the workflow:

* **Draft**: The workflow has not been published.
* **Active**: The workflow has a published version and can accept runs.
* **Inactive**: The workflow is paused. Its published version is retained, but new runs and tests are disabled until it is activated.

## Workflow Versions

A workflow version is a snapshot of its canvas, selected resources, mappings, and module configuration.

* A new workflow starts with a draft version.
* A published version is read-only and continues to run until it is replaced.
* Selecting **Edit** on a published version creates a new draft.
* Changes to the new draft do not affect the published version.
* Publishing the draft makes it the active version.

Use **Workflow versions** in the editor to view and switch between available versions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.docupilot.app/workflows/test-publish-and-version-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.