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

# Version history

Morphic keeps a version of a workflow each time it changes. Version history shows every one of them, who made it and when, and lets you put an earlier version back in use.

This is what makes editing a shared workflow safe. If a change did not work out, or a teammate changed something you relied on, the version before it is still there.

Here's a quick tutorial on how to use version history on Morphic:

### Open version history

1. Go to [Workflows](https://studio.morphic.com/workflows)
2. Hover the workflow you want and click the '···' menu on its card
3. Click 'Version history'

The workflow opens with the version list on the right, newest first and grouped by month. Each entry shows the time it was made and who made it, so on a workflow your team shares you can see who changed what.

### Look at an earlier version

1. Click any version in the list
2. The workflow appears as it was then, with the inputs and steps it had at the time
3. A bar at the bottom of the screen shows which version you are viewing

Looking at an old version changes nothing for anyone else. The workflow your team runs stays the current one until you publish a different one.

To stop looking and return to the current version, click 'Cancel' in that bottom bar.

### Put an earlier version back in use

1. Open the version you want
2. Click 'Publish version' in the bottom bar
3. A dialog names the version you picked. Click 'Publish Version' to confirm

That version becomes the one everyone uses to run the workflow.

The versions made after it stay in the list. Going back is not the same as throwing away what came later, so you can move forward again the same way you moved back.

### Work on a copy instead

When you want to try something without touching a workflow other people are running, duplicate it and work on the copy.

1. Hover the workflow and click the '···' menu
2. Click 'Duplicate'

The copy is a workflow in its own right. It starts from the version you copied and builds its own history from there, and the original carries on unchanged.

### Good to know

* Looking at an old version changes nothing for anyone. Only publishing does.
* Publishing an earlier version does not remove the ones made after it, so you can move forward again the same way you moved back.
* On a workflow your team shares, the list names who made each version, which is the quickest way to find out what changed and who to ask.

That's how version history works on Morphic. Use it to go back to an earlier version, or to try a change on a copy first.

***

If you have any trouble or have any questions, feel free to reach out. We're happy to help. Write to us at [**support@morphic.com**](mailto:support@morphic.com)**.**


---

# 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://morphic.com/docs/workflows/version-history.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.