Automation runs fine in Studio/Testing, fails when scheduled

[justindward (Justin Ward)]

Hi, I’m scheduling my first daily unattended automation. It runs perfectly when I trigger it from the Studio, but it has only succeeded once out of maybe a dozen times when it’s triggered from Orchestrator.

It’s a UI automation that downloads a spreadsheet from a city website, reshuffles the columns, runs a Python script to add more data and reuploads it to my Google drive.

In the automation I have set up lots of delays to wait until the UI element appears and also a long 15-second delay to wait for the export to initiate and the download to complete.

However, when I run it from the UiPath Assistant to test, it doesn’t delay and closes the browser window before the file export initiates, so the next activity “Copy File” fails because the file doesn’t exist.

Is there some setting in the orchestrator configuration that tells it to ignore the delays in my original automation when running it from a scheduled trigger? If so, how do I change that?

[ashokkarale]

@justindward,

Instead of specifying fix delay you should be using Wait for Download activity. This will ensure your browser will not be closed before the download completed.