# How to resolve Error 409: “You cannot update a pipeline that is not on draft mode”
## Understanding how pipelines work
Pipelines are the core of the Digibee Integration Platform. They consist of a sequence of connectors that allows you to connect systems and establish data flow between them. Learn more in the [Pipeline documentation](/documentation/developer-guide/development-cycle/build-overview/pipelines.md).
Each pipeline has a [version history](broken://spaces/jvO5S91EQURCEhbZOuuZ/pages/PkMz16oFtXSARL6zUehX) that lists all minor versions within its major version, making management easier. This version history includes the last editor, the date of the changes, and an optional description of the changes.
Whenever you create or change a pipeline, a new minor version is added to the version history.
## When does Error 409 occur?
Error 409 occurs when you try to save changes to a pipeline that is no longer in draft mode. This often happens when:
1. You complete creating or editing the pipeline.
2. Deploy the version in a different tab.
3. Return to make new changes to the previously saved pipeline.
The moment you click Save, a pop-up window appears with Error 409 stating that the pipeline cannot be edited because it has already been deployed and is therefore no longer in draft mode.
## Steps to fix and prevent Error 409
### Fixing the error
If you had already edited the pipeline when this error occurred, perform the following steps to save your changes:
1. Copy the part of the flow that you changed.
2. Open a new tab and access the pipeline in draft mode.
3. Paste the flow into the pipeline.
4. Save your changes.
This ensures that the changes are made successfully and a new minor version is created.
### Preventing the error
To prevent Error 409, refresh the page where you created your pipeline after deployment or reopen the pipeline in draft mode to make new changes.
---
# 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://docs.digibee.com/documentation/troubleshooting/deployment-issues/error-409.md?ask=
```
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.