Workflow Hangs During UI Interaction - Selector Healing Seems Stuc

Feedback Healing Agent
1

I’m working on a project in Studio using the Modern Design Experience and I’m running into an issue where my workflow hangs during a UI interaction.

The Problem:

My workflow opens a browser (Edge) to the URL. After the browser opens, the automation gets stuck. It doesn’t throw an error immediately, but the execution does not proceed. The last log message I see is the “Audit: Using Web App…” message from the Use Application/Browser activity. And then hangs with message “{
“message”: “Healing agent configuration.”,
“level”: “Information”,
“logType”: “Default”,
“timeStamp”: “15:04:10”,
“fileName”: “Download Generic County”,
“jobId”: “85e2dhhhh-50e4-4152-8320-78754d693fbd”,
“robotName”: “or@gmail.com-attended”,
“machineId”: 5505563,
“userKey”: “4c7f504f-96a5-4570-8127-be05bff4f62d”,
“processVersion”: “1.0.0”,
“organizationUnitId”: xxxxx,
“healingAgentConfig”: {
“orchestratorEnableHeal”: false,
“orchestratorEnableAnalysis”: false
},
“businessxxxxxxx0ad545d3a-3ef34489f657e1308c6”
}”

When I run in Debug mode, the execution pauses, but no specific activity is highlighted in yellow. It seems to be hanging on a UI interaction inside the Use Application/Browser scope.

What I’ve Observed:

  • The issue seems to be related to an activity trying to find a UI element on the page after it loads.

  • I suspect the Selector Healing agent is getting triggered and is unable to resolve the selector, causing the process to hang until it times out.

  • I have tried creating a new

Use Application/Browser

activity, but the problem persists.

My Question:

  1. Has anyone experienced a situation where the workflow hangs without highlighting a specific activity in Debug mode, especially when a UI selector is likely failing?

  2. What is the best way to debug an issue like this when the debugger doesn’t point to a specific activity? Are there other logging or debugging techniques I can use to find the exact point where it’s getting stuck?

  3. Could this be related to the page loading behavior (e.g., a pop-up, a slow-loading element, or a redirect) that is preventing UiPath from finding the target element?

Any advice on how to troubleshoot this “hanging” behavior would be greatly appreciated.

2

@Phil_Kelsey
It looks like the bot is getting stuck because it’s waiting for a UI element that never actually becomes available. Instead of throwing an error, it just keeps waiting inside the ‘Use Application/Browser’ scope which makes it seem like the workflow is hanging.

Please do the following

  1. Use activities like ‘Wait for Element Appear’ or ‘Check App State’ before interacting with any elements. This makes sure the page is fully loaded before the bot continues.

  2. f the application or page is slow to load, the default timeout might not be enough. Extending it can prevent unnecessary waiting.

Note : If you’re expecting the Healing Agent to handle selector issues, double check that it’s enabled in Orchestrator.