---
title: "Catching All Unconnected Outcomes"
slug: "catch-outcome-step"
tags: ["Error Handling", "catch", "exception"]
updated: 2022-10-24T18:46:22Z
published: 2022-10-24T18:46:22Z
canonical: "documentation.decisions.com/catch-outcome-step"
---

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

# Catch Outcome Step

| ## Step Details |
| --- |
| **Introduced in Version** | --- |
| **Modified in Version** | --- |
| **Location** | Flow Management > Error Handling |

The **Catch Outcome** step can be configured to trigger when step outcome paths are not connected to the Flow. This step can be used to clean up or simplify Flows, by grouping several of the same outcome paths that are expected to follow the same Flow logic.

---

## Properties

#### Catch Outcome

| Property | Description | Data Type |
| --- | --- | --- |
| OutcomeType |
|  | All | Catches all outcome paths | --- |
|  | SpecifiedPaths | Allows the user to specify the outcome paths to catch | --- |
|  | SpecifiedPathAndData | Allows the user to specify the outcome paths and the defined output data to catch | --- |
|  | ContainingData | Allows the user to specify the defined output data to catch | --- |

#### Outputs

| Property | Description | Data Type |
| --- | --- | --- |
| Complete |
| Previous Step ID | Outputs the previous Step Id | String |
| Previous Step Name | Outputs the previous Step Name | String |
| Previous Step Path | Outputs the previous Step path | String |

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1666636480523.png)

---

Related Information

Forum Posts: [Catch Exception in Email Flow (with Counter)](https://support.decisions.com/forum/topic1248-catch-exception-in-email-flow-with-counter.aspx)

##

## Related

- [Catch Exception Step](/catch-exception-step.md)
- [Throw API Exception with Headers](/throw-api-exception-with-headers.md)