Error Handling in Automation Edge

Get Help & Discuss Process Studio
1

What are best practices for error handling in AutomationEdge workflows?

2

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.