Conditions within the Interrupt handler enables you to define a specific criteria for triggering or executing actions based on variables, values, or states within your automation flow. By setting up conditions, you can ensure that the Interrupt handler only responds to particular events or data, making your automation more precise and controlled.

Conditions

Condition Description
Recorder
  • Use the Object exists condition to detect an object in a window. Select a window or variable to capture the object.

    When used in an Interrupt handler, this condition continuously monitors for the presence of the defined object. If the object appears, the Interrupt handler is triggered, allowing you to execute a specified set of actions (such as handling pop-ups, alerts, or unexpected UI changes).

  • Use the Object does not exist condition to verify whether a specific object absent in a window.

    This condition is used to trigger the Interrupt handler when the defined object is no longer present. It’s useful for responding to scenarios where a window or dialog closes, or a UI element disappears. For example, resume or adjust automation when a loading spinner disappears, indicating the process can continue.