> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/workflows/task-transitions.md).

# Task transitions

## **What are task transitions?**

*Task transitions* are the bridges that connect different action, ensuring that workflows move forward as designed. Each action has two circular nodules on its side and bottom.  Click on either and drag to the next action to set up the transition. Depending on the criteria set, one action might branch out to multiple subsequent actions.&#x20;

<figure><img src="/files/CIgjcSYTGlhlunTydfHc" alt=""><figcaption><p>An action with no set transition - note the two circular <strong>Add Transition</strong> bubbles</p></figcaption></figure>

The diamond that appears between the two actions once the transition has been created is called the *transition indicator*. Click on it to open the transition settings in the right side menu.&#x20;

<figure><img src="/files/M5rGHEadNrGZWkdSJwzw" alt=""><figcaption><p>The transition indicator for a dragged action that has had its transition created</p></figcaption></figure>

## **Transition settings options**

<figure><img src="/files/snPAcpBpVK4UBX0ZRsH6" alt=""><figcaption></figcaption></figure>

* **Edit Transition**: Buttons beside the **Edit Transition** title give you options to either clone the current transition or remove it if it's no longer needed.
* **Custom Transition Label**: This is an editable field allowing you to give a meaningful name to the transition, aiding clarity as your workflow grows.
* **Condition**: This criteria governs the action's progression based on the options defined below. Depending on the outcome of this action, this rule determines which path to follow next. Left to right, these are:
  * **On Success**: Progress if the action succeeds.
  * **On Failure**: Progress if the action fails.
  * **Always**: Progress regardless of the outcome of the action.
  * **Custom Condition**: This is set custom, with Jinja.
* [**Data Aliases**](/documentation/automations/workflows/data-aliases.md): Click the **+ Add Data alias** button to define an easy-to-use variable that stores the results of the action transition.

{% hint style="success" %}
In the advanced options in the workflow body, you can opt to either follow the first left to right transition condition that returns true, or to follow all transitions from the action.
{% endhint %}

Right click on any transition indicator to open a submenu to **Duplicate Transition,** **Delete Transition**, or **Edit Transition Order**. Duplicate will recreate the exact transition and place it next to the original on the Workflow Builder Canvas. Edit Transition Order controls the sequence in which transitions are evaluated and executed. Transition order at any given time is indicated by numbers on the transition indicators. Learn more about this setting in our [Advanced Workflow Settings](/documentation/automations/actions-in-rewst.md) documentation.

<figure><img src="/files/tPMzeGSa58ojp16EMCSm" alt=""><figcaption></figcaption></figure>

## Transition modes

Settings for transition modes exist in the **Advanced** tab of the workflow's settings. For information on how these work, see our documentation for [advanced workflow operations](/documentation/automations/workflows/advanced-workflow-operations-menu.md#transition-modes).&#x20;


---

# 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:

```
GET https://docs.rewst.help/documentation/automations/workflows/task-transitions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
