> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-user-manual/dashboard/missions/mission-handling.md).

# Mission handling

Example of mission handling.

Mission objects are used to store time-limited measurements, such as transport monitoring.

### Example mission object

A mission object called **Transports** contains: 

* 3 **virtual mission MPs** called `-22 -18°C`, `2-6°C`, and `2-8°C`
* 3 **real mission MPs** called `TPatrol sensor 1`, `TPatrol sensor 2`, and `TPatrol sensor 3`

The real mission MPs receive readings directly from BTiny mission sensors.

<figure><img src="https://3588014471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEANwXRnuP0ug8971viyg%2Fuploads%2F8JkASrB15VpOYv4b2KrG%2Fimage.png?alt=media&amp;token=9a8b2aa1-1624-413e-a1ba-5f45bcd4ba8f" alt=""><figcaption></figcaption></figure>

### Real vs virtual mission MPs

* **Real mission MP**: represents a physical BTiny mission sensor. This is where readings arrive first.
* **Virtual mission MP**: a “bucket” you can use to organize mission results. Typical use is grouping by a target range (for example, `2-8°C`).

### Typical workflow

1. Start the mission and collect readings in a **real mission MP** (one per sensor).
2. After the mission ends, review the mission data.
3. If needed, move or copy mission data into a **virtual mission MP** to group missions by use case or temperature range.

### Related pages

* [Missions](/boomerang-3-user-manual/dashboard/missions.md)
* [BTiny Mission sensor usage](/boomerang-3-user-manual/dashboard/missions/btiny-mission-sensor-usage.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 by asking a question.

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

```
GET https://help.boomerang3.com/boomerang-3-user-manual/dashboard/missions/mission-handling.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.