> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing/router-versions.md).
# Router versions
Saving router edits creates a draft. **Activation** makes a version available for new routing attempts. This applies to Form, Click, and Outbound Routers.
Make your changes, save them, and use **Test route** to check the saved draft. Activate when you're ready for new prospects to use it.
## What changes for existing prospects?
A prospect who has already started keeps the router version they began with. This lets them finish with the configuration used for their original attempt.
Calendars, user availability, and current access are still checked. A saved version doesn't reserve a host or make a busy time available.
## Return to an earlier version
Open **Versions** to review the router's published history. **Roll back** changes the version used by new, unpinned traffic. It doesn't replace the version of an attempt already in progress or remove your saved draft.
If a link was deliberately pinned to a version, a rollback doesn't change that pin. Check pinned links when a particular test or campaign continues to show older behavior.
## Shared settings
Routers capture configuration such as event settings in their activated versions. After changing shared configuration, review and activate the router version that should use it.
Outbound Forms are also adopted explicitly. Publishing a newer form alone doesn't advance routers that use an older version.
## Test and duplicate
**Test route** simulates the saved configuration. It does not book a meeting, write CRM records, or call enrichment providers. Use representative inputs, then check the real entry point after activation.
Duplicating a router creates a separate router without an active version. Review and activate the copy before using it. Referenced rules, event types, and forms can still be shared; a duplicate is not an independent copy of every connected setting.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.distro.so/routing/router-versions.md?ask=&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 `automate deployments from our CI pipeline` 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.
