> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/missions/how-to-guides/manage-running-missions.md).

# Manage Running Missions

Once Missions are [scheduled](/missions/how-to-guides/schedule-a-mission.md) and live on mobile boards, admins need tools to intervene — prioritize urgent work, unblock stalled tasks, remove unnecessary instances, and export data. This page covers the day-to-day actions available from the web.

## Why do you need these actions?

Schedules handle the routine, but real operations aren't routine. A holiday means today's cleaning missions should be canceled. An employee leaves mid-shift with 5 claimed Missions stuck on the board. A VIP guest arrives and the setup task needs to jump to the top immediately. These actions give you control over what's already running.

All actions below are performed from [**Overview → Running**](/analytics-and-monitoring/overview/track-running-missions.md) on the web, unless noted otherwise.

## <mark style="color:purple;">Boost a Mission</mark>

Manually move a Mission to the **top of the board** and mark it as high priority — so employees see it first.

### How to boost

**On the web:** Overview → Running → select a Mission → context menu or sidebar → **Boost** (flag icon).

**On mobile:** Open Mission details on a [Team Board](/mobile-app/your-mobile-boards.md#team-board) → tap the **flag icon** → enter [Personal Code](/your-organization/people.md#personal-code).

Boosted Missions display a **red timer** and a **flag icon**. When multiple Missions are boosted, you can **reorder** them to set priority among boosted items.

To remove the boost: select the Mission → **Unboost**. The timer reverts to its normal color.

### Who can boost

[System Admins, Organization Managers](/your-organization/people.md#roles), and Employees with Observer permissions. Regular Employees (Members) cannot boost.

### Where boosting works

* Missions on [Team Boards](/mobile-app/your-mobile-boards.md#team-board)
* Tickets on all [Ticket Boards](/your-organization/ticket-boards.md)
* Missions in the [On Demand library](/missions/how-to-guides/trigger-a-mission-out-of-schedule.md)
* Only **Open** Missions can be boosted
* [Personal Board](/mobile-app/your-mobile-boards.md#personal-board) items cannot be boosted manually

{% hint style="info" %}
Boosting can also happen **automatically** via the [Boost Mission on Timer](/missions/how-to-guides/configure-mission-settings/ensuring-work-gets-done-on-time.md#boost-mission-on-timer) setting. This page covers the manual action.
{% endhint %}

## <mark style="color:purple;">Cancel a Mission Instance</mark>

Remove a single [Mission](/mobile-app/perform-a-mission.md) instance from all boards. The schedule stays intact — only this one occurrence is affected.

### How to cancel

**On the web:** [Overview → Running](/analytics-and-monitoring/overview/track-running-missions.md) → select an Open or Claimed instance → **Cancel Instance** from the action bar or context menu.

**On mobile:** Open a Mission on a [Team](/mobile-app/your-mobile-boards.md#team-board) or [Ticket Board](/mobile-app/your-mobile-boards.md#ticket-board) → tap **Cancel** → enter [Personal Code](/your-organization/people.md#personal-code). (Not available on Personal Boards from mobile.)

Canceled instances disappear from mobile boards but remain visible in Overview with "Canceled" status for reporting purposes.

### Bulk Cancel

Need to cancel many instances at once (e.g. a holiday shutdown)?

Overview → Running → **Bulk Actions** → **Cancel** → select instances with checkboxes → confirm. Works across Team, Personal, Ticket, and Process Boards.

### Good to know

* Only [**Open** and **Claimed**](/mobile-app/perform-a-mission.md#claim-a-mission) instances can be canceled
* Future scheduled instances are **not affected** — they'll generate as planned
* Once canceled, an instance **cannot be reactivated** — wait for the next scheduled occurrence or reschedule
* Cancel Instance removes one occurrence. To stop all future occurrences, use **Clear Schedule** instead (see [Schedule a Mission](/missions/how-to-guides/schedule-a-mission.md))

## <mark style="color:purple;">Bounce Back a Mission</mark>

Return a Claimed Mission to the **Open** state so someone else can pick it up. The previous assignee is removed.

### How to bounce back

**On the web:** [Overview → Running](/analytics-and-monitoring/overview/track-running-missions.md) → select a Claimed Mission → **Bounce Back** from the action bar or context menu. Works for [Team, Personal, and Ticket Boards](/mobile-app/your-mobile-boards.md).

**On mobile:** Open a Claimed Mission on a Team or Ticket Board → tap the **back arrow** → enter [Personal Code](/your-organization/people.md#personal-code). (Not available on Personal Boards from mobile.)

The Mission immediately returns to the Open column on all boards.

### Bulk Bounce Back

End of a shift with 12 unclosed Missions? Overview → Running → **Bulk Actions** → **Bounce Back** → select Claimed instances → confirm. All selected Missions return to Open simultaneously.

### Good to know

* Only **Claimed** Missions can be bounced back
* Bouncing back **clears all progress** saved by the previous claimant
* There is **no undo** — if bounced back accidentally, the Mission must be reclaimed
* For automatic bounce-back after a set time, enable [Auto-Bounce Back](/missions/how-to-guides/configure-mission-settings/ensuring-work-gets-done-on-time.md#auto-bounce-back) in Mission Settings


---

# 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://documentation.taskmaverick.com/missions/how-to-guides/manage-running-missions.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.