# Task transitions

## **What are task transitions?**

*Task transitions* are the bridges that connect different tasks, ensuring that workflows move forward as designed. They're represented by the small rectangles found directly beneath each task. Depending on the criteria set, one task might branch out to multiple subsequent tasks. When you interact with these rectangles by clicking on them, a configuration menu appears. Note that this is a different menu from what is seen when you click on the task itself.

<figure><img src="/files/bMWAeWz0Wl1gBr39UmjT" alt=""><figcaption><p>A task transition, nested under a generic task</p></figcaption></figure>

## **Task transition configuration options**

<figure><img src="/files/F92fMKdPR9bRuAxlCb0F" alt="" width="359"><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 Label**: An editable field allowing you to give a meaningful name to the transition, aiding clarity as your workflow grows.
* **Move Left/Right**: These are controls that allow you to rearrange the sequence in which transitions are evaluated and executed. Transitions are evaluated from left to right, so order them carefully.
* **Condition**: This criteria governs the task's progression based on the options defined below. Depending on the outcome of this task, this rule determines which path to follow next. Left to right, these are:
  * **Success**: if the task succeeds
  * **Failure**: if the task fails
  * **Always**: regardless of the outcome of the task
  * **Custom Condition**: set custom, with Jinja
* [**Data Aliases**](/documentation/automations/workflows/data-aliases.md): Clicking the **+** button lets you define an easy-to-use variable that stores the results of the task 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 %}

## Transition modes

For information on how these work, see our documentation for [advanced workflow operations](/documentation/automations/workflows/advanced-workflow-operations-menu.md#transition-modes).


---

# Agent Instructions: 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.