> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monobot.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Pass / Fail Conditions

## Overview

Pass / Fail conditions define how your flow continues after an action is executed.

Each action can have two pre-configured outcomes:

* **Pass** — the action completed successfully
* **Fail** — the action failed (error, validation issue, external service failure, etc.)

These outcomes allow you to build **controlled, reliable, and fault-tolerant flows**.

<Frame>
  <img className="block" src="https://mintcdn.com/monobot-0e0ffe36/yVZ9w6FeuKr7UZXp/images/settings/actions/conditions/p_f_conditions.png?fit=max&auto=format&n=yVZ9w6FeuKr7UZXp&q=85&s=34b1a711648aa251f02dacb719dd05af" alt="Pass/Fail Conditions" width="3000" height="1621" data-path="images/settings/actions/conditions/p_f_conditions.png" />
</Frame>

## How It Works

When an action is executed:

* If it succeeds → the **Pass path** is triggered
* If it fails → the **Fail path** is triggered

Each path can lead to a different next step in your flow.

***

## Basic Logic

Action → Pass → Next Step A\
→ Fail → Next Step B

***

## Example: Summary → Email

### Flow:

1. Summarize Conversation
2. If successful → send email

### Logic:

* If summary is generated → proceed to email
* If summary fails → stop or handle separately

***

## Example: Email with SMS Fallback

### Flow:

1. Generate summary
2. Send email
3. If email fails → send SMS

### Logic:

Summary → Pass → Email\
Email → Pass → End\
Email → Fail → Send SMS

***

## Real Use Case

### Scenario:

* Primary communication: Email
* Backup channel: SMS

### Behavior:

* If email is delivered → flow ends
* If email fails → SMS is sent automatically

***

## Why Use Pass / Fail

### Reliability

Handle failures gracefully instead of breaking the flow.

### Flexibility

Different outcomes can trigger different logic paths.

### Better UX

Users still receive communication even if one channel fails.

***

## Best Practices

* Handle Fail paths
* Use fallback channels (Email → SMS)
* Keep flows simple

***

## Common Patterns

### Success Chain

Step 1 → Pass → Step 2 → Pass → Step 3

### Fallback Handling

Email → Fail → SMS

### Conditional Recovery

API Call → Fail → Alternative

### Silent Failure

Optional Step → Fail → Continue

***

## Notes

* Pass/Fail depends on action execution result
* Design flows assuming failures can happen

***

## Summary

Pass / Fail conditions allow you to:

* control execution flow
* handle errors properly
* build resilient automations