Auto-Healing Agent

Help Orchestrator
, ,
1

We are currently testing Auto-healing Agent in our Orchestrator processes. However when enabled, it fails to identify UI Elements the need to be fixed.

After completion of processes, it states, “The job was successfully completed without any issues requiring self healing.” However after reviewing the logs, there are a couple of instances where UI elements are not found, or failed.

2

@ashton.lalchan

  1. If it is check app state or element exists it would not heal as it is just checking for existance
  2. If it is failing on any clicks then ideally it should be caught if not please report the same…also it depends on how the selectors have been used as well

Cheers

3

Can you elaborate on #2 because when have a few processes with this error where it should ideally pick up and heal:

[Target]: Could not find the UI element corresponding to this selector:
[1]
[2]
[3]
[4]

Search failed at selector tag:
[4]

The closest matches found are:
[66%]
[66%]
[66%]
[58%]
[57%]
[56%]
[55%]
[55%]
[54%]
[54%]

4

@ashton.lalchan

Looks like you are using classic activities if so it does not work…it works on modern only…also your robot and ui packages sgould be 24.12 + …project should be windows or cross platform

These are current limitations

This image lists various limitations of a software Healing Agent, including support restrictions and detection issues with external applications and UIAutomation activities. (Captioned by AI)
This image lists various limitations of a software Healing Agent, including support restrictions and detection issues with external applications and UIAutomation activities. (Captioned by AI)828×1187 218 KB

Cheers

1 Like