> 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/loop-back-to-a-previous-step.md).
# Loop back to a Previous Step
A Transition Activity lets your Process jump back to an earlier step — creating retry loops for scenarios where an employee needs to redo something before moving forward.
***
## Why use Transition Activities?
Some workflows are inherently iterative. An employee fails a safety test → they need training → then they retake the test. Without Transition, you'd need to duplicate Activities or build a separate Process. With Transition, the Process loops back naturally.
***
## How to set it up
1. Open a Process in the Builder
2. Add a **Transition Activity** on level 2 or deeper
3. In the Activity's Settings, configure:
Field
Options
Title
Name this step (e.g. "Retry Test")
Transit To
Choose where to jump: Start of the Process (restart everything) or any previous Activity in the same branch
4. Save
{% embed url="" %}
***
## What happens when a Transition fires
1. The Process instance **stays the same** — no new Process is created
2. The target Activity is **re-triggered** on the same board
3. Any Activities between the Transition and the target that are still active (Open or Claimed) are **canceled**
4. Activities that were already completed **stay completed**
5. After the jump, the Process continues forward from the target Activity as usual — evaluating Conditions and triggering next steps normally
***
## Real-world example
**Safety test with retry loop:**
1. Employee takes a safety Test (level 1)
2. If they score below 70%, a training Media Mission is triggered (level 2)
3. After completing the training, a Transition Activity sends them back to retake the Test (jumps to level 1)
4. This loop continues until they pass
5. When they pass, the Process moves to the next step
***
## Good to know
* Transition Activities **cannot have** [**Conditions**](/processes/how-to-guides/build-a-process.md#add-conditions) — they simply redirect the flow
* Must be the **last Activity in their branch** — nothing can come after a Transition
* Cannot be referenced in other Activities' Preconditions ([Skip logic](/processes/how-to-guides/skip-an-activity.md))
* Re-triggered Activities appear **multiple times** in Overview, Reporting, and the Process Trail
* Transition Activities also support **Preconditions** (Skip logic) — so you can conditionally skip the loop itself
---
# 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/loop-back-to-a-previous-step.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.