> ## Documentation Index
> Fetch the complete documentation index at: https://plera.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Runs

A Run is a named campaign container created from a Play. It keeps the selected strategy, lead sources, sequences, messages, status, and analytics together for one outbound motion.

## What a Run stores

* The selected Play.
* The campaign name.
* Discovery searches, clues, imports, or manual sources tied to the campaign.
* Sequences created for eligible enriched leads.
* Message drafts, review state, launch state, replies, and analytics.

<Frame caption="Show a Run with its selected Play, lead sources, sequences, launch state, replies, and analytics visible together.">
  <img src="https://mintcdn.com/plera/a_5u0pLU0fMK2aMa/images/placeholder.png?fit=max&auto=format&n=a_5u0pLU0fMK2aMa&q=85&s=3d523a5cb5a93496a9254fc05ee1dd92" alt="Placeholder for Run workspace" width="1440" height="1024" data-path="images/placeholder.png" />
</Frame>

## Run lifecycle

```text theme={null}
Draft -> Active -> Paused or Completed
```

Draft Runs are still being prepared and reviewed. Active Runs have live sequence activity. Paused Runs temporarily stop new sending. Completed Runs have finished sequence steps for eligible leads.

## Why Runs are separate from Plays

A Play can be reused many times. Each Run applies that Play to a specific lead source, strategy profile, sender account, and campaign goal.