Orchestrator TimeOut Issues while scheduling job from Back Office

Help
1

Hello RPA Folks,

I have scheduled a process in Orch scheduled to run at a specific day and time. But when ever it starts running , in details tab I see–> Installing package. and after 2 mins it shows Time Out and process fails. Please tell how to cure this ? This is being run on RDP machine with UiPath version -

Process : PROCESS_P1![Capture|289x295]
Package : PKG1
Robot : ROBOT11
Info : “The operation has timed out”
Start Time : “2019-01-02T12:00:05.33Z”
End Time : “2019-01-02T12:01:46.753Z”

Also uploading UiPath version.

Capture

Please help

2

@AdityaShivam

I think the bot is taking more time to login. So we have to increase the default Timeout MS.

Regards,
Mahesh

3

Thanks Mahesh , How and where do you do this please ?

4

@AdityaShivam

Refer this post, It will help you.

Regards,
Mahesh

5

There is a note there : Note: This workaround is available for the latest versions (v17.1.6435.21855 and 2016.2.6437.26235)

My UiPath version is : 2016.2.6379

6

@ClaytonM
@PrankurJoshi
@loginerror
@ovi
@badita

Please can anyone of you experts know a fix to this ?

7

There could be a few problems.
—Your UiPath version is 2016.2, so there could be many of these issues fixed now - I recommend updating to version 2018
—Windows Server 2012 might have a Start screen when you first log in by default, which you can see this by manually signing off then logging in again - if it doesn’t go straight to the Desktop on that machine (not the Start Screen), then there could be a problem - if this is the case, consult your IT to suppress this setting so it goes straight to the Desktop.

It’s most likely due to your UiPath version.

Note: if you publish a job that only Takes Screenshot, this can show what the screen looks like when you run it from Orchestrator - however, if it still gets the Timeout error, then check what the screen looks like when you manually log in, like I mentioned.

If this or the troubleshooting guides on the forums don’t help, then escalate a ticket HERE

Regards.

1 Like
8

—Your UiPath version is 2016.2, so there could be many of these issues fixed now - I recommend updating to version 2018 – NOTED

—Windows Server 2012 might have a Start screen when you first log in by default, which you can see this by manually signing off then logging in again - if it doesn’t go straight to the Desktop on that machine (not the Start Screen), then there could be a problem - if this is the case, consult your IT to suppress this setting so it goes straight to the Desktop.

–we reach desktop directly once we log in.

9

@ClaytonM

Is there a way to restart the job automatically if it fails due to timeout failure of Orchestrator.

If I use cron expression , then that will require additional handling to make sure that it do not run again if it has successfully completed .

10

I don’t believe Orchestrator has a retry feature like that. But, I have not used 2018.4 so not sure about newest version.

Either way, you ideally want your job to have logic in place where if it happens to run more than once for whatever reason, it can with no issues. For example, if it downloads a file, it should either be able to overwrite that file or detect that it already exists so it skips that item. Another thing to consider is that if a certain day fails to run, your job should be able to process each day that it missed within a certain range of days (this has saved me many headaches)

Also, your job should be able to detect errors and decide what to do with it, like for example, retry to process an item that had caused an error for a number of attempts.

But, to your question, I don’t think Orchestrator can see a failed job and perform a retry on that job. It’s a feature I’m interested in though.

EDIT: It also depends on the error, cause some are server side so retrying the job might actually cause issues rather than help (like if password is wrong for that robot)

1 Like
11

Hello @ClaytonM , Since UiPath orchestrator recognizes the issues and can classify it, i think they cn come up with a solution of Re-running the bot again, in cases like timeout. But yes if it is wrong id/password. It should not re run.