Use cases for Healing Agent

Frequently changing user interfaces result in changes to static selector attributes. This causes automations to fail.

In this scenario, Healing Agent detects the selector changes, generates a new selector dynamically, validates and re-executes the activity.

In applications with responsive design, UI layouts may shift due to changes in screen size or resolution. This causes automations to fail, as the anchor is no longer in the expected position.

In this scenario, Healing Agent recognizes anchors even when their positions shift in relation to the target, adapts the automation in real-time, and ensures that automation tasks are executed accurately.

Pop-up windows may obstruct target UI elements in your automations. This is a common occurrence in applications that use notifications, error prompts, or modal windows. This causes automations to fail, as the target element is blocked.

Healing Agent detects any target element even when it is obstructed, it automatically closes the pop-up or modal window, and then validates and re-executes the activity.

Applications may load slowly due to system performance, network delays or other reasons. This can cause automations to fail when automations attempt to execute actions before the target application finishes loading.

In this scenario, Healing Agent determines when a target element is ready or not, it waits the required amount of time, and then validates and re-executes the activity.

Target elements in applications are not static, and can change. For example, a Submit button may be renamed to Confirm by the application developers.

In this scenario, Healing Agent autonomously identifies that the renamed element has an identical underlying functionality, it updates the automation to align with the modified interface, and then validates and re-executes the activity.