Intermittent Timeout / Not Connected Error in Get Text at Position (UiPath.Terminal.Activities, EHLLAPI)

Help Activities
, , , ,
1

I’m facing an intermittent issue while using the Get Text at Position activity in UiPath.Terminal.Activities. Occasionally, the activity throws a timeout or not connected error. However, when I retry the same transaction item, the activity executes successfully without any issues.

This problem occurs only for a few items and is not consistent. I am using the EHLLAPI emulator method with package version 2.9.0, and I have also tested with 2.8.2, but the behavior remains the same.
The same activity is used in multiple places within my workflow, and the error appears randomly in different sections each time.

Has anyone experienced similar intermittent failures or found a stable approach to handle this? Any suggestions would be helpful.

2

You are getting error, because the screen may not be fully visible/ready by that time.

You can wait for screen to be available, then extract text.

Use check app state to see if screen or uielement is availble, then extract using get text.

Also place get text in retry scope..

3

I am waiting until screen gets loaded

It is terminal automation right I think the above mentioned uiAutomation activities will not work

4

Hi @akhil_n.v

As per my knowledge ,Wrap the Get Text at Position activity in a Try–Catch and use a Retry Scope with 2–3 attempts and short delays. In the Catch block, disconnect and reconnect the EHLLAPI terminal session before retrying. Ensure no heavy parallel processes are running that may interfere with the terminal. Optionally, consider using UI automation mode for more stability.

Happy Automation

5

@akhil_n.v

As this is an intermittent issue, I would suggest to add the get text into the Retry Scope