This problem seems to be occurring with multiple web sites.
But I am unable to figure out , the same UiPath work flow when we run on a different system (Win 7 Lenovo T460) ,
works like charm and creates no delay whatsoever.
I dont understand why is it not working on the original Laptop (Win 7 Lenovo T460) and both the laptops have same configurations.
Could it be system specific issue?
If yes , could you please advise how do we progress with this.
any solution for this issue.
even though UiPath can find the web element, it uses all the timeout time that it has. as a standard 30 sec, if reduced to 2 sec, it will do the action after 2 sec. this is not optimal.
error is in 2017.1 SP1
Yeah, I would say the problem is actually the WaitForReady = INTERACTIVE property.
I saw the same slowness problem in one portion of one screen in the application that was being automated.
In some cases, when it was changed to COMPLETE or NONE, that fixed the problem,
but what the option had to be seemed to depend on the computer, so maybe the UiPath or
Internet Explorer version was different.
The portion of the web page, where the slowness appeared, seemed to be dynamically generated, so
maybe this has something to do, with the page or element loading on webpages. I would have expected
though that the INTERACTIVE option would have been the fastest, instead of the slowest, since it waits
only for a portion of the page to be loaded as far as I know.
I have no clear specs, but this is known about the systems, where this problem occurred:
I have exactly the same behavior at the the same exercise (Download monthly report). In the beginning it runs fine. In my case I used an example that had no reports available up to July. Then at July it finds a report, downloads it and every action after that is slow and takes roughly 30 seconds.
Weird thing is, if you Stop (F12) the workflow during execution and try to run it again from the beginning, it will then be slow from the beginning (so also Jan - June in my example). To reset the whole machine, you then first need to Close Internet Explorer AND UiPath Studio.
Could there be some bug with the For Each loop or the activities inside the Else part?
WaitForReady=None seems to speed up again, but Interactive and Complete sometimes necessary (e.g. Vendorinformation in the training environment).
@ovi Testing on Windows 7, IE11 and Studio 2017.1.6522
I am facing the same problem. However, it got solved by setting WaitForReady = None. This is probably just a temporary solution, or could this work long-term? What are the drawbacks of using this “quick fix”?
When downloading monthly reports from Acme-test.com, it suddenly get a lot slower.
Windows 10, IE11, Studio 2017.1.6522.
Thank you all for this discussion. I have been breaking my head for weeks to figure out the issue. As most of you have isolated that this delay is happening once we have interacted with a file download dialogue. Quite surprised to see that this issue have not been resolved yet!
hi, i haver the similar problem, but for example, when i run olnly this (System1_CreateYearlyReport.xaml (32.2 KB)
)process for create yearly reports whitout the main process. it was executed perfectly, and it was created this report, (Yearly-Report-2017-FR065748.xlsx (8.0 KB)
) i dont know why failed when excecuted the main process
For me the problem was solved, once I formatted my Windows OS and had a fresh installation of Win 7> installed UiPath on my laptop again >worked fine for me ,
I’ve had this happen to me to on Windows 10. It just randomly decides to go slow. I am running a single xaml file and the first Type Into took about 30 seconds to achieve. I am using the Acme “Download Monthly Report”. The first iteration of the workflow execution, although I ran it before through its full cycle.
Same problem over here
Every interaction with the ‘Reports - Download Monthly Report’ page takes up to 2 (!) minutes. The rest of the bot runs smoothly.
Hey, UiPath-people, I cannot afford that amount of time!
I’m facing the same issue. after downloading the first file the UIpath is taking very long time to find the elements and perform the activities inside the browser but the activities related to Save window are faster. (Activities related to browser are very slow)