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

# Executions

An Execution is the record of a single run of a Pipeline. It contains all the information about that run - when it was run, who ran it, what data was produced etc.

Nextflow pipeline runs consist of a series of invidual processes, which run in their own self contained environment and have their own inputs and outputs. These are chained together to form the entire pipeline execution. You can see all the processes that executed within an Execution (or watch them running live if the run is ongoing). You can also see all the Data that is produced.

Executions and Data together form a network, with Data nodes feeding into Execution nodes, which themselves produce more Data nodes.


---

# 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://docs.imaps.goodwright.com/fundamentals/executions.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.
