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

# Lifecycle

How a workflow goes from draft to deployed, review gates, and code-off workspaces.

```
Create → Save (draft) → Publish (snapshot) → Deploy (to an environment)
```

| Stage       | Effect                                                               |
| ----------- | -------------------------------------------------------------------- |
| **Save**    | Persists the draft. Nothing goes live.                               |
| **Publish** | Creates v1, v2, … A snapshot, so rollback is deploying an older one. |
| **Deploy**  | The version starts handling real events in that environment.         |

An environment can be marked **Requires review**. Promoting to one of those opens a pull request on the connected GitHub repository instead of deploying straight away: the setting is per environment, and lives on [Environments](/manage/environments.md), which is also where the repository is connected.

### When code editing is switched off

Code editing is a per-workspace setting, and **off in almost every workspace** (it is enabled only for the parent organisation. Where it is off, a banner says so, and the editor simply has no code column: workflows are generated and updated by the AI builder, and you change behaviour by talking to the [agent](/build/agent.md) rather than editing the file. Everything else is unchanged), you still test, wire connectors, edit the contract, publish and deploy, and the runtime surface is identical. It can be switched on if you want to write workflow code yourself; ask fastn to enable 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/build/workflows/lifecycle.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 `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.