---
title: "Error Node"
slug: "error-node"
description: "Learn how to configure the Error node in your workflow to handle component errors effectively and redirect users seamlessly."
updated: 2025-11-25T20:14:32Z
published: 2025-12-09T16:46:27Z
canonical: "docs.unqork.io/error-node"
---

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

# Error Node

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Error_Node_Intro.webm?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A35Z&se=2026-11-07T18%3A57%3A35Z&sr=c&sp=r&sig=F4xCBkjQRqi9vNzJWTzZN8HI6J5jJ0ltv7pnfKKFfN0%3D)The **Error node** redirects a [workflow](/v1/docs/introduction-to-workflow) when the [Plug-In](/v1/docs/plug-in-component) component of an automated [Task](/v1/docs/task-node) node module returns an error. In the Workflow Builder, the Error node attaches to that Task node in the [Automated](/v1/docs/swimlane-management) swimlane.

It’s important to note that if your [Plug-In](/v1/docs/plug-in-component) component already contains an error trigger, your Error node will not catch the error and redirect.

You’ll find the Error node in the list of nodes to the left of the [Workflow Builder](/v1/docs/introduction-to-workflow).

## Error Node Settings

After adding an Error node to your workflow, select it to open a **Settings Menu**. This menu displays as a blue menu bar, either above or below the node itself. The menu has the following options:

![Workflow example showing an editable error node labeled 'errorEvent-1'.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/errrorNode.webp?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A35Z&se=2026-11-07T18%3A57%3A35Z&sr=c&sp=r&sig=F4xCBkjQRqi9vNzJWTzZN8HI6J5jJ0ltv7pnfKKFfN0%3D)

| **Setting** | Description |
| --- | --- |
| **Edit** | Takes you to the Edit Error Event drawer, where you can configure related settings. |
| **Delete (Down Arrow)** | Removes the node from the workflow |

### Edit Error Event Drawer Description

The following settings are available in the Edit Error Event drawer:

![Editing an error event with the label 'errorEvent-1' in a user interface.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/errorNodeDrawer.webp?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A35Z&se=2026-11-07T18%3A57%3A35Z&sr=c&sp=r&sig=F4xCBkjQRqi9vNzJWTzZN8HI6J5jJ0ltv7pnfKKFfN0%3D)

| **Setting** | Description |
| --- | --- |
| **Label** | Sets the name of your node. By default, the Label displays as `errorEvent-1.` The label you enter here is optional and displays below the node on the workflow canvas. Define your labels by associating them with the node’s role. |

## Adding an Error Node

In this example, the workflow confirms if an end-user wants an error returned. If your end-user selects **No**, your workflow proceeds and returns a message retrieved from a transform. If your end-user selects **Yes**, the [Plug-In](/v1/docs/plug-in-component) component in the second [Task](/v1/docs/task-node) node simulates an error. Then, your Error node returns the end-user to the first Task node to answer the question again.

> [!NOTE]
> This demonstration is for illustrative purposes only and cannot be replicated due to [Training](https://training.unqork.io/) environment security.

### Configure the Task Nodes

Add three [Task](/v1/docs/task-node) nodes to your workflow. The first Task node connects to the [Start](/v1/docs/start-node) node. The second Task node uses [Plug-In](/v1/docs/plug-in-component) components to simulate an error response. The final Task node returns a message if no error occurs.

1. Drag and drop two **Task** nodes into the **Authenticated** swimlane.
2. Select a **Task** node.
3. Click **Edit**.
4. In the **Label** field, enter `Input`.
5. From the **Module** drop-down, enter or select `Enablement Labs: Error Node Use Case-Input`.

> This demonstration module asks end-users if they want to generate an error in the next Task node.
6. Click **X** (Close).
7. Select the second **Task** node.
8. Click **Edit**.
9. In the **Label** field, enter `Result`.
10. From the **Module** drop-down, enter or select `Enablement Labs: Error Node Use Case-Result`.

> This demonstration module contains two Plug-In components. One Plug-In component functions as expected, the other is configured incorrectly and triggers the Error node.
11. Click **X** (Close).
12. Drag and drop a third **Task** node into the **Automated** swimlane.
13. Click **Edit**.
14. In the **Label** field, enter `Error Check`.
15. From the **Module** drop-down, enter or select `Enablement Labs: Error Node Use Case-Error Check`.

> This demonstration module displays if end-users choose not to trigger the error node.
16. Click **X** (Close).
17. Connect the output port (right) of the **Start** node to the input port (left) of the `Input` **Task** node.
18. Connect the output port (right) of the `Input` **Task** node to the input port (left) of the `Error Check` **Task** node.
19. Connect the output port (right) of the `Error Check` **Task** node to the input port (left) of the `Result` **Task** node.

### Configure the Error Node

Next, add an Error node. Your Error node redirects the workflow path if a [Plug-In](/v1/docs/plug-in-component) component error occurs.

1. Drag and drop an **Error** node onto your` Error Check` **Task** node. [Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/errorNodeDrop.webm?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A35Z&se=2026-11-07T18%3A57%3A35Z&sr=c&sp=r&sig=F4xCBkjQRqi9vNzJWTzZN8HI6J5jJ0ltv7pnfKKFfN0%3D)
2. Click **Edit**.
3. In the **Label** field, enter `Error Event`.
4. Connect the output port (bottom) of the **Error** node to the input port (left) of the `Input` **Task** node.
5. Click **X** (Close).

### Configure the End Node

1. Drag and drop an **End** node into the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `End`.
4. Connect the output port (right) of the `Result` **Task** node to the input port (left) of the `End` **End** node.
5. Click **Save...**.
6. **Save** your workflow.

Your completed workflow looks like the following:

[![Workflow diagram illustrating error node processes and connections in a system.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/errorNodeWorkflow.webp?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A35Z&se=2026-11-07T18%3A57%3A35Z&sr=c&sp=r&sig=F4xCBkjQRqi9vNzJWTzZN8HI6J5jJ0ltv7pnfKKFfN0%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Error%20Node%20Lab%20Complete.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A35Z&se=2026-11-07T18%3A57%3A35Z&sr=c&sp=r&sig=F4xCBkjQRqi9vNzJWTzZN8HI6J5jJ0ltv7pnfKKFfN0%3D)

Preview your workflow. From the Error selection, select **Yes**. The workflow progresses to the Automated lane, and the Error node triggers, redirecting the end-user to the Error selection task. Click **No**, and the workflow progresses to the Result task.

A UI (User Interface) Drawer is a layout panel that slides out from the side of the screen to display content. In UDesigner, components display their configuration panels in a drawer.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.