# Configuring Saga Steps

Saga flows start with a single START node and can have one or more SUCCESS / FAIL nodes as the exit point. Other nodes are linked as sequential steps in between them and have the following common parameters:

* **Name:** Descriptive name of the step, which will be displayed on saga graph
* **Description:** Detailed description of what this step will perform
* **Stroke:** Stroke color of the step on saga graph
* **Fill:** Fill color of the step on saga graph
* **Auto Fail:** Whether saga should automatically fail if this step fails
* **Continue on Fail:** Whether saga step should continue on fail (to override in case saga itself is configured as Auto Fail)

### Step types

Saga graphs are built from a small set of step types. Each type has different configuration fields and runtime behavior.

#### Control steps

These steps define entry and exit points of the flow:

* **Start:** Entry point for the saga execution.
* **Success:** A successful exit point.
* **Fail:** A failure exit point.

#### Action and logic steps

These steps do the work between Start and exit nodes:

* [Event Step](/devops/api-event-and-process-flows/configuring-saga-steps/event-step.md): calls an event handler action with parameters.
* [Transform Step](/devops/api-event-and-process-flows/configuring-saga-steps/transform-step.md): transforms the current payload and passes the output forward.
* [Condition Step](/devops/api-event-and-process-flows/configuring-saga-steps/condition-step.md): evaluates a condition and routes to different next steps.

#### Connecting steps

* [Step Link](/devops/api-event-and-process-flows/configuring-saga-steps/step-link.md): defines how the flow moves from one step to the next. Use condition values to model branching and default (`*`) paths.

{% hint style="info" %}
Double clicking on a step on stencil automatically adds it as a connected step for the currently selected node on saga flow.
{% endhint %}


---

# 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.rierino.com/devops/api-event-and-process-flows/configuring-saga-steps.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.