Skip to main content

Exception Handling in Talos

In any automated workflow, errors are inevitable. Whether it's a network glitch, a missing file, or a UI element that didn't load in time, Exceptions are the way Talos signals that something went wrong during execution.

Talos provides a robust framework to manage and recover from these errors through Exception Rules.

How Talos Handles Errors​

Error handling in Talos is driven by Rules that you define for each action. These rules dictate what happens when a specific Exception Type occurs.

Exception Rules​

Instead of a simple "on/off" error switch, Talos uses rules to give you granular control. Within an action's properties, you can define rules that tell Talos to:

  • Retry the action automatically.
  • Ignore the error and keep going.
  • Abort the execution if the error is critical.
  • Go to a specific action (defining the "On Error" path).

The "On Error" Connection​

In the Workflow Designer, you may see an On Error outgoing connection on an action. This connection is defined by an Exception Rule of type Go to Action.

When you set a rule to "Go to Action" for a specific exception (or for "ALL" exceptions), you are effectively telling Talos: "If this error happens, follow the On Error path to this specific action."

Core Concepts​

To master error handling in Talos, you should familiarize yourself with:

  • Exception Types: Understanding what kind of errors can occur (Playback, Detection, System, etc.).
  • Error Handling Rules: Learning how to configure retries, ignore logic, and error branching (Goto Action).
  • Throw Exception Action: How to intentionally trigger an error based on your own business logic.