> 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/processes/how-to-guides/monitor-processes.md).

# Monitor Processes

Once a Process is published and running, you need visibility into what's happening — which instances are active, which Activities are stuck, and which Processes completed successfully.

## Why monitor Processes?

Automation is powerful, but not invisible. Equipment breaks, employees call in sick, conditions change. Monitoring lets you catch stalled workflows, identify bottlenecks, and verify that your Processes are actually delivering results.

## How a Process runs

{% stepper %}
{% step %}

#### A [Trigger](/processes/how-to-guides/set-up-process-triggers.md) fires

On schedule, when a Mission is closed, or when someone launches it on demand.
{% endstep %}

{% step %}

#### Level 1 [Activities](/processes/how-to-guides/build-a-process.md#add-activities) are posted

Level 1 Activities are posted to their destination boards.
{% endstep %}

{% step %}

#### Employees [complete Missions](/mobile-app/perform-a-mission.md)

Employees see regular Missions on their mobile boards and complete them as usual.
{% endstep %}

{% step %}

#### Conditions are evaluated

When an Activity is completed, the system evaluates its [**Conditions**](/processes/how-to-guides/build-a-process.md#add-conditions).
{% endstep %}

{% step %}

#### Next-level Activities are triggered

Next-level Activities are triggered based on the results.
{% endstep %}

{% step %}

#### The Process continues

The Process continues level by level until all required Activities are completed.
{% endstep %}
{% endstepper %}

Employees don't need to know a Process exists — they just see Missions appearing on their boards at the right time.

## Process statuses

<table><thead><tr><th width="183.3333740234375">Status</th><th>What it means</th></tr></thead><tbody><tr><td><strong>Initiated</strong></td><td>First-level Activities are posted, none claimed yet</td></tr><tr><td><strong>In Progress</strong></td><td>At least one Activity has been claimed</td></tr><tr><td><strong>Completed</strong></td><td>All required Activities are closed</td></tr><tr><td><strong>Canceled</strong></td><td>Manually canceled, or a required Activity was canceled</td></tr><tr><td><strong>Terminated</strong></td><td>Cannot continue due to an error</td></tr></tbody></table>

## Monitoring on the web

Go to **Overview → Process Board** to track all running Processes:

<table><thead><tr><th width="187.333251953125">Tab</th><th>What it shows</th></tr></thead><tbody><tr><td><strong>Running</strong></td><td>Processes currently initiated or in progress — which Activities are active, who's working on them, how long they've been running</td></tr><tr><td><strong>History</strong></td><td>Completed, terminated, or canceled Processes — review outcomes and timing</td></tr><tr><td><strong>Deployed</strong></td><td>Published Processes with active Triggers — verify your configuration is correct</td></tr></tbody></table>

## Reporting

For deeper analysis, go to [**Reporting → Process**](/analytics-and-monitoring/reporting/report-sections-at-a-glance.md#process):

<table><thead><tr><th width="205.3333740234375">Report</th><th>What it tells you</th></tr></thead><tbody><tr><td><strong>Process Details</strong></td><td>Full breakdown of individual instances — every Activity, status, and timestamp</td></tr><tr><td><strong>Process Summary</strong></td><td>High-level metrics across all instances of a Process</td></tr><tr><td><strong>Average Duration</strong></td><td>How long each Process and its Activities typically take</td></tr><tr><td><strong>Activity Frequency</strong></td><td>Which Activities are triggered most/least often — helps identify bottlenecks</td></tr></tbody></table>

## What employees see on mobile

Mobile users see Process Activities as regular Missions. Two extra elements give them context:

**Trigger Details** — visible in Mission details. Shows which Process this belongs to, which previous Activity triggered it, who completed the previous step, and what condition was met.

**Process Trail** — a visual chain showing completed steps, the current step, and planned next steps. Helps employees understand how their work fits the bigger picture.

## How mandatory and optional Activities behave

| Setting                            | While running     | When Process completes                  |
| ---------------------------------- | ----------------- | --------------------------------------- |
| **Required = Yes**                 | Must be completed | —                                       |
| **Required = No, Cancel Activity** | Runs normally     | Auto-canceled                           |
| **Required = No, Keep Activity**   | Runs normally     | Stays active for the employee to finish |

## Good to know

* **Delay Activities** are not visible on mobile — they run silently in the background
* If a Mission is already on a board and the Process triggers the same Mission there, it **won't duplicate** — Process info is attached to the existing Mission
* A Mission can belong to **multiple Processes** — it shows multiple Process Trails
* If an Activity uses [References](/your-organization/organization-settings.md#reference-management), it creates one instance per Reference Unit
* Processes can only be **canceled** from the web ([Overview → Running](/analytics-and-monitoring/overview/track-running-missions.md) → Cancel)


---

# 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/processes/how-to-guides/monitor-processes.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.