> For the complete documentation index, see [llms.txt](https://code-collective.gitbook.io/launch-flow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://code-collective.gitbook.io/launch-flow/get-started/core-concepts.md).

# Core concepts

### Launches

A **launch** is a scheduled change with a time attached. Each launch moves through states you can see in the dashboard: *Scheduled* (waiting), *Live* (applied), *Rolled back* (reverted), or *Failed* (something prevented it, see [Troubleshooting](/launch-flow/reference/troubleshooting.md)).

### Snapshots

Before Launch Flow changes anything, it saves a **snapshot** of the original values for prices, that's the existing amount on each product. The snapshot is what makes a clean rollback possible: Launch Flow always knows exactly what to restore.

### Scheduled events

Your plan determines how many launches can be scheduled at once. The Free plan allows **one** scheduled event at a time; paid plans allow more (see [Plans & limits](/launch-flow/reference/plans-and-limits.md)).


---

# 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://code-collective.gitbook.io/launch-flow/get-started/core-concepts.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.