- Identify which part is lagging and change WaitForReady from interactive/complete to none
which solution are you referring to? I might have missed it…
follow the solution i given above as that is what i and many others faced in the past while working on that assignment.
as for timeout while saving csv files, i have no idea what is the issue
which solution are you referring to? I might have missed it…
i mean the above
past example
Hi
I cannot understand what’s wrong… I’ve followed the guidelines but it’s slow and after the 1st
file getting saved, it goes on to the next queue message.
Do you mind if I share my process to have a look or it doesn’t work that way?
Nikos
I experienced delays during this assignment. I believe its a UiPath side issue as we needed their team to carry out some maintenance to the target app.
Even if it does, I cannot complete the assignment and finish this training… and time flies…
sure just send the files here
hi all
coming back to this, as i’ve not found a solution yet:
-
cannot invoke the “Save As” option
-
my process is as follows:
-
when running the process, i see this toolbar on IE flashing:
-
and the following errors in the Output window:
Click ‘Button’: Cannot find the UI element corresponding to this selector:
Invoke System1_Create_YearlyReport workflow: Cannot find the UI element corresponding to this selector: <wnd title=‘OK’ />
System exception.Cannot find the UI element corresponding to this selector: at Source: Invoke System1_Create_YearlyReport workflow: Click 'Button’
I’ve confirmed that
Any support is more than welcome
1 Like
Also noticed that my process name is System1_CreateYearlyReport but i get the error from System1_Create_YearlyReport which is neither found in my System1 folder, nor has been invoked from Process.xaml…
So with the data you have provided, 2 things
- the issue is not in the part where you are checking the issue is i think i when its going to the else part of the if condition.
- The invoke name can be different to the xaml name. you can verify it.
is this running now?
yes.