> 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/stop-mission.md).
# Stop mission
You can stop an immediate mission and a scheduled mission in the same way.
{% stepper %}
{% step %}
### Open the mission sensor MP
Click the mission sensor MP (for example, `TPatrol sensor 1`) in the Dashboard.
{% endstep %}
{% step %}
Transport Control buttons are located on the right side of the mission field.
{% endstep %}
{% step %}
### Stop the mission
Click **Stop mission** and sign.
If you use a **BTINY009** sensor which is within wireless range of a **Cloud Connector**, you can also stop the mission from the sensor by pressing its tactile switch.
A scheduled mission can be stopped the same way. It also stops automatically at its predefined stop time.
BTINY009
{% endstep %}
{% step %}
### Review the completed mission
After you stop the mission, it appears in the mission list.
The graph and list views show the mission data.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
See [Mission object view](/boomerang-3-user-manual/dashboard/missions/mission-handling/mission-object-view.md) for where the Mission field and controls are located.
{% endhint %}
---
# 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/stop-mission.md?ask=&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.
are located on the right side of the mission field.
{% endstep %}
{% step %}
### Stop the mission
Click **Stop mission** 
and sign.
If you use a **BTINY009** sensor which is within wireless range of a **Cloud Connector**, you can also stop the mission from the sensor by pressing its tactile switch.
A scheduled mission can be stopped the same way. It also stops automatically at its predefined stop time.
