Interrupt handler package

Interrupt handler package improves automation resiliency by identifying and managing unexpected in-product pop-ups that might occur during automation or task execution.

These pop-ups can disrupt workflow and might need human intervention such as a click or entering user credentials. When any of the set interrupt conditions happen during a task, the system runs the corresponding actions in the block called Handle. All the possible interrupts are checked in a sequence that is defined in the automation. The Interrupt Handler ensures that automations are executed without any interruptions by handling these events.
Note: A system check is done for the remaining defined interrupts after running the associated actions.

Considerations

Review the following considerations for using the Interrupt handler in your automation:
  • If you use the Stop action in the Handle action block, it will stop the execution of the entire automation.
  • Interrupts are not checked or verified while executing the actions in the handler section.
  • If an interrupt handler block is added inside the Handle action, system will not look for those interrupts.

Sample use case

Consider a sample use case where you have built an automation to process invoices from a shared network folder and upload them to an Enterprise Resource Planning (ERP) system. Possible interruptions to your automation are:
  • Handle1: Log in prompt to the network folder
  • Handle2: Session timeout pop-up of the ERP system.
  • Handle3: Window security pop-up
A sample automation flow is as follows:
  • Open the network folder and access the invoices.
  • Read the invoices and upload the data into the ERP system.
  • Send a confirmation email.

If the session timeout pop-up of the ERP system appears during automation execution, Handle 2 is triggered. The interrupt is detected immediately and the actions inside the Handle2 are executed and another log in attempt is initiated. After resolving the interrupt, the automation proceeds to the next step of uploading the invoices without checking the Handle 1. A confirmation email is triggered after the upload completes.

The various possible pop-ups are handled without any interruptions to the automation deployment and minimum user intervention.

Actions in the Interrupt handler package

The following actions are available:

Action Description
Scope See Scope.
Handle See Handle.