> For the complete documentation index, see [llms.txt](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/campaign-owners/campaign-status-and-controls.md).

# campaign status and controls

The campaign profile shows the current lifecycle status and available actions.

## Common statuses

| Status    | Meaning                                                          |
| --------- | ---------------------------------------------------------------- |
| In Review | The campaign is waiting for approval and is not yet circulating. |
| Active    | The campaign is eligible for matching and delivery.              |
| Inactive  | The campaign is paused and is not currently delivering.          |
| Aborted   | The campaign was dropped before normal completion.               |
| Expired   | The campaign reached the end of its cycle window.                |

Other administrative or eligibility statuses may appear when Boom•Clap needs to intervene.

## Pause

Select **Pause Campaign** to stop new circulation without dropping the campaign. Already-recorded reporting remains available.

## Resume

Select **Resume Campaign** to return an inactive campaign to circulation. Resume succeeds only when the campaign is eligible and the account has enough available Melody Credits for the remaining budget.

Campaigns do not resume automatically after a refill.

## Drop

Select **Drop Campaign** when the campaign should not return to circulation. Dropping is different from a temporary pause and should be treated as a terminal owner action.

## Content changes

Clients cannot freely edit campaign content from the live profile. This includes the campaign URL, cover, subject image, description, geography, and branded-publisher preference.

Contact Boom•Clap when a material correction is necessary. Administrative edits can be made with appropriate clearance.


---

# 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://being-and-time.gitbook.io/boom-clap-melody-field-guide/campaign-owners/campaign-status-and-controls.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.