---
category: [Platform and Product Extensions/Workday Extend, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations, Administration & Integrations/Custom Integrations & Apps]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: Handle Errors
layout: subsection
---

### Prerequisites

<a id="prereq_N10021_N1001E_N10001"></a>
Create an orchestration.

### Context

<a id="context_N10028_N1001E_N10001"></a>
Orchestration Builder enables you to create local error handlers for components and groups of components. You can also create global error handlers to specify what action to take when an error isn't caught locally.

### Steps

1.  <a id="step_N10032_N1002F_N1001E_N10001"></a>To add a local error handler, click the related actions menu on the relevant step or group of steps and select <b>Add Error Handler</b>. Orchestration Builder opens a separate canvas for the local error handler and its steps.

    The error handler doesn't have access to any outputs produced by the step to which the error handler is attached. It begins with the same data they began with, plus an additional output called `processingError`, of Processing Error type, which provides access to the error's location.

    The error handler can't directly access the exception message of the failing step. However, you can optionally use the <b>Log</b> component to log the message.

2.  <a id="step_N1003F_N1002F_N1001E_N10001"></a>Select the error handler to open its Properties panel, and provide a <b>Reference Name</b>.
3.  <a id="step_N1004C_N1002F_N1001E_N10001"></a>Select <b>Conditional Outputs</b> or <b>Propagate Error</b>.

    The Propagate Error option processes any steps you add to the error handler and rethrows the error to the parent error handler or, if no parent exists, to the global error handler.

    The Conditional Outputs option processes any steps you add to the error handler and outputs a boolean value called `isSuccess`.

    If the step or group of steps to which the error handler is attached execute successfully, the `isSuccess` output takes the value `true`. Both it and the outputs of the step or group of steps are available downstream.

    If the error handler's steps don't execute successfully, the `isSuccess` output takes the value `false`. Only it is available downstream.

    You can use the `isSuccess` output in branching logic to determine how the error is handled.

    Downstream steps should access the primary outputs of the step to which the error handler is attached only conditionally, using the `isSuccess` output as the condition. If downstream steps attempt to access the primary outputs of a failed step, Orchestration Builder rethrows the error.

    <b>Note:</b> You can't use the <b>Conditional Outputs</b> option in an error handler attached to the last step in an orchestration or a group of steps.

    Outputs produced by the error handler's last step aren't propagated downstream, so they don't need to be compatible with other outputs.

4.  <a id="step_N10068_N1002F_N1001E_N10001"></a>Add components to the error handler as required. To return to the main canvas, click the name of your orchestration in the breadcrumb trail above the components panel.
5.  <a id="step_N10071_N1002F_N1001E_N10001"></a>To add a global error handler, click the <b>Global Error Handler</b> button (lightning bolt icon) at the top of the interface. As it does with a local error handler, Orchestration Builder opens a separate canvas for the global error handler and its steps.