# Error Handling in Automation Edge

**URL:** <https://community.automationedge.com/t/error-handling-in-automation-edge/17903>\
**Category:** Process Studio\
**Created:** [May 4, 2026, 12:10pm UTC](https://community.automationedge.com/t/error-handling-in-automation-edge/17903 "2026-05-04T12:10:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![876785](https://avatars.discourse-cdn.com/v4/letter/8/67e7ee/32.png) [@876785](https://community.automationedge.com/u/876785)\
**Post date:** [May 4, 2026, 12:10pm UTC](https://community.automationedge.com/t/error-handling-in-automation-edge/17903/1 "2026-05-04T12:10:08Z")

</div>

What are best practices for error handling in AutomationEdge workflows?

---

<div class="post-metadata">

**Author:** ![AETrainings](https://avatars.discourse-cdn.com/v4/letter/a/2acd7d/32.png) [@AETrainings](https://community.automationedge.com/u/AETrainings)\
**Post date:** [October 5, 2026, 11:39am UTC](https://community.automationedge.com/t/error-handling-in-automation-edge/17903/2 "2026-10-05T11:39:59Z")

</div>

In AutomationEdge, robust error handling relies on choosing the right mechanism across three distinct structural levels:

- **Step-Level Error Handling Hops:** Configured directly on individual steps to redirect failing rows down an error path without terminating execution. It captures specific error variables like `Number of Errors`, `Error Description`, `Error Code`, `Error Field`, and `Error Step Name`. This pattern is ideal for fine-grained row validation or API retries, but applying it to every step creates canvas clutter.

- **Block-Level Try-Catch Steps:** `Try` and `Catch` steps are placed in pairs to handle errors across an entire block of steps simultaneously. The `Catch` step captures error metadata and routes failed rows to designated target steps. This keeps complex business transactions readable, though it requires adherence to strict pairing and loop-alignment rules.

- **workflow / Process Level:** High-level processes (`.psp`) and specialized steps (such as `Abort` from the Flow plugin, `Write to Log`, or `Audit Log`) manage overarching execution state, retries, logging, and failure notifications.