Exceptions
Just like programming and scripting languages A-Ops has a concept of exceptions that can be used when triggers and actions crash or flows overrun the maximum defined duration.
Triggers support exception handling that will cause A-Ops to call another flow via the trigger ID you define.
Defining Exception Handling
Its easy to get started using the exception handling functionality:
- Open a trigger object within the conduct editor
- Select "Exceptions" tab
- Enter the trigger ID of the trigger you want to be called and corresponding flow executed when an expiation is raised within "On Trigger Crash", "On Trigger Killed" or "On Action Crash"
Exception Handlers
On Trigger Crash
An underlining exception was raised during the trigger check function or while executing the flow.
On Trigger Killed
Maximum duration of the trigger was exceeded and as a result the trigger was killed by the A-Ops worker.
Fail Trigger On Action Crash
Ensures that a single action exception that was raised results in the entire trigger crashing preventing future execution or events from being processed.
On Action Crash
When "Failed Trigger On Action Crash" is checked then any exceptions that are raised by any action will trigger this exception handler.