Orchestrator issue – The operation has timed out


#1

Hi all,
I am having an issue with contacting Orchestrator from UiPath activities.
I get the following error for activities like Get Asset, Add Queue Item… basically anything that tries to connect to orchestrator. What is strange is that this does not always happen, but only sometimes and without changing anything. So I’ll run the workflow and it can add the queue item, and I run it again and suddenly I get this error.

image

I have no trouble manually connecting to orchestrator (browser), the robot is successfully connected to orchestrator (otherwise it would NEVER work) and the Queues and Assets are correct.
So I don’t get how this can happen and it is really important since this is always supposed to work.
I have last versions of UiPath (2018.2.3) and Orchestrator (2018.2.3).
Anyone has any idea on what could be the cause?


#2

Hi @Brett22 do you have any log file?
Location: “c:\users\AppData\Local\UiPath\Logs”


#3

Here is the message and stacktrace of the error and below is the log message obtained. I did this only with a test workflow which have a Get Asset activity inside a try catch, that’s all.

16:42:55.7806 Info {“message”:“partage execution started”,“level”:“Information”,“logType”:“Default”,“timeStamp”:“2018-07-05T16:42:55.6746601+02:00”,“fingerprint”:"",“windowsIdentity”:"",“machineName”:"",“processName”:“partage”,“processVersion”:“1.0.6738.28122”,“fileName”:“test”,“jobId”:"",“robotName”:""}
16:42:57.1117 Error {“message”:“MESSAGE : The operation has timed out… STACKTRACE : at UiPath.Core.Activities.BaseAssetActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)\r\n at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)\r\n at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)”,“level”:“Error”,“logType”:“User”,“timeStamp”:“2018-07-05T16:42:57.1117243+02:00”,“fingerprint”:"
",“windowsIdentity”:"",“machineName”:"",“processName”:“partage”,“processVersion”:“1.0.6738.28122”,“fileName”:“test”,“jobId”:"",“robotName”:""}
16:42:57.1117 Info {“message”:“partage execution ended”,“level”:“Information”,“logType”:“Default”,“timeStamp”:“2018-07-05T16:42:57.1157228+02:00”,“fingerprint”:"",“windowsIdentity”:"",“machineName”:"",“processName”:“partage”,“processVersion”:“1.0.6738.28122”,“fileName”:“test”,“jobId”:"",“robotName”:"*",“totalExecutionTimeInSeconds”:1,“totalExecutionTime”:“00:00:01”}


#4

Hey @Brett22
That seems to happen because of some server issues sometimes, if you’ll try a little later it may work again, could you try reconnection your robot to the orchestartor?


#5

Hey,
This has happened since I updated everything to the last version, so it is not temporary as it has happened everyday.
And yes I have tried removing the robot from orchestrator and reconnecting it (kind of like resetting everything).
The strangest thing is that it happens randomly.
For instance, I have tried to put it in a loop and execute the Get Asset activity 100 times. Well sometimes it got all OK, sometimes 70 failed, others 60, others 10… it seems completely random.
This is quite a crucial aspect for the project and I could put loops everywhere I call orchestrator but it wouldn’t be quite convenient.


#6

@Brett22, did you manage to get this issue resolved? I’m having a similar issue ‘The operation has timed out’ with a ‘get transaction item’ activity from the Orchestrator