About error "Terminal Error: Timeout"

Help
,
1

Hello,

Im developing a project using Mainframe terminal (Micro Focus Reflection)
When robot running on customer environment, Timeout error sometime occur but on development environment, timeout error didnt occur.

This error appear on any activity Send Key or Send ControlKey.
I dont know the root cause why terminal has timeout.

Can anyone help me on this error?

System.Exception: Terminal error: Timeout
場所 UiPath.Terminal.Activities.TerminalActivity`1.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
場所 System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
場所 System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

2

I have the same error? how you solved this?

3

Hi @Fabio_Oliveira,

Welcome to UiPath community.

I think this error occur when robot cannot receive signal from terminal. you can try below steps

  1. Increase the timeout limit of the terminal activity.
  2. Check the connection between the robot and the terminal to ensure that the robot is receiving signals from the terminal.
  3. Check the terminal settings to make sure that it is configured correctly.
  4. Check the terminal logs to see if there are any errors or warnings being displayed.
  5. Check for any network or firewall issues which may be preventing the robot from communicating with the terminal.
  6. Check for any software or hardware issues which may be causing the timeout error.
  7. Try restarting the terminal activity to see if the error can be resolved.

Thanks,

4

It depends which activity is generating the error.

5

I already increased the Timeout time to 150000, I also see that the terminal is connected, I don’t have any of the problems you are referring to

follow the print of the error

image
image1857×924 166 KB

6

follow the print with the activity that has the error.

image
image1543×951 106 KB

7

That screenshot shows a different error, FieldNotFound.

Anyway, the terminal “wait” activities throw a timeout error if they don’t find what they were told to wait for, within the timeout period. It’s not the greatest design for these activities, but it is what it is. They don’t work like Element Exists where they return a true/false. They either find what they are waiting for and the automation continues, or they throw an error. You’ll have to put a Try around it to Catch the error.

8

Sorry, I already corrected this error. what i’m really talking about is this

image
image1857×924 166 KB

9

You’re using a 3rd party terminal client that does not show it’s in the Ready state (bottom left).

These kind of issues are common when using 3rd party terminal clients, and there isn’t anything you can do about it except put a Retry Scope around any activity where it’s happening.

You should be using Direct Connection. It’s far more stable and reliable. You won’t see these kind of issues.