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

# Test, publish, and versions

Saving, publishing, and accepting new events are separate controls. Check each one before sending real traffic.

## Save the draft

Builder changes save to the draft. Wait for **All changes saved**, or select **Save draft**.

The published version continues to handle live events until a new version is published. Do not use an unsaved preview as proof of what is live.

## Validate

Select **Validate** and review **Workflow checks**. Fix missing configuration, invalid references, unavailable connections, and resources that are not ready.

Validation checks configuration and supported contracts. It does not confirm a real provider request, calendar booking, or website installation.

## Simulate

Select **Simulate**. Enter trigger inputs and supply output samples for external steps.

Simulation follows the draft's paths using those samples. It does not send the provider actions. Test success, no match, unassigned, and error paths deliberately.

Use simulation to answer “does this configuration take the right path?” Use a controlled real test to confirm the connected system.

## Publish and turn On

Select **Publish** once the saved draft is ready. Publication creates a version of the workflow.

Review the **On / Off** control. It controls acceptance of new workflow events. Publication and workspace activation do not mean the same thing.

Then activate the source:

| Source                  | Final setup                                                                          |
| ----------------------- | ------------------------------------------------------------------------------------ |
| Native lead form        | Select the published workflow version in Change routing, save, and publish the form. |
| Connected external form | Select a compatible published version and activate the connection.                   |
| Webhook or schedule     | Complete Webhook setup or Schedule setup and verify acceptance.                      |
| Extension or API        | Confirm the caller can access and start the published workflow.                      |
| CRM events              | Confirm the CRM connection, object, start conditions, and subscription readiness.    |

If the workspace has enrollment or execution paused, ask your admin or Distro support to activate it. Turning a workflow On cannot override that workspace restriction.

## Run a live test

Where available in Simulate, choose **Run for real against the published version**.

Live tests are supported for webhook, API, schedule, and extension triggers when workspace execution and enrollment are enabled. Other triggers need a controlled test through their actual source.

{% hint style="warning" %}
A live test can update CRM records, send messages, call webhooks, and consume provider usage. Use controlled records and recipients.
{% endhint %}

## Review versions

Open **Versions** to inspect published versions. Historical versions open read-only.

Use the restore control to bring a previous version back into the draft, review it, then publish it if you want new traffic to use it.

Runs already in progress keep their starting workflow version. Shared resources, such as queue membership, profile settings, and event hosts, still need their own review.

## Pause thoughtfully

Turning Off stops new enrollment; it does not undo completed actions. Review existing runs separately, and cancel a specific run only when your process calls for it.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/workflows/test-and-publish.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.