> 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/skip-an-activity.md).
# Skip an Activity
Sometimes a step in your [Process](/processes/what-are-processes.md) only applies in certain scenarios. Instead of building separate branches for every case, you can tell the system to skip an [Activity](/processes/what-are-processes.md#key-concepts) automatically when a condition is met.
## Why use Skip?
Real workflows have exceptions. A quality check Process for candy bars might include a "Check chocolate amount" step — but that step makes no sense for a Protein bar that has no chocolate. Without Skip, you'd need two separate Processes. With Skip, one Process handles both cases elegantly.
## How to set it up
1\. Open a Process in the Builder
2. Select an Activity on **level 2 or deeper**
3. Skip isn't available on level 1 — there's no previous Activity to evaluate.
4. Click the **+** button in the **Precondition** section
{% stepper %}
{% step %}
Field
What to select
If in Activity
Choose a previous Activity in the same branch
Condition
Define the rule (same condition types as regular Activity Conditions — response, rating, timer, etc.)
Action
Skip Activity
{% endstep %}
{% endstepper %}
5. Configure
6. Save
{% embed url="" %}
## What happens when a Precondition is met
* The Activity is **not triggered** — employees never see it
* Activity status is set to **Skipped**
* The Process **continues** to the next Activity automatically
* Skipped Activities are visible in the **Process Trail** on mobile and in the **Process** view on web
## Real-world example
**Candy bar quality check:**
A Process checks quality for two candy bar types — Chocolate and Protein. Almost all checks are identical, but step 5 is "Check chocolate amount" — only relevant for Chocolate bars.
The Precondition: "If in Activity 1 (Candy Bar Type), the response is 'Protein' → Skip this Activity."
Result: Protein bars skip step 5 automatically. Chocolate bars go through it. One Process, both scenarios covered.
## Good to know
* Skip is available for **all** [**Activity types**](/processes/how-to-guides/build-a-process.md#add-activities)
* Only works on **level 2 and deeper** — the first level has no previous Activity to evaluate
* The Precondition references Activities in the **same branch on earlier levels** only
* Skip Activity is a precondition behavior — it's different from Conditions between levels (which decide what triggers next)
---
# 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/skip-an-activity.md?ask=&goal=
```
`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.