Check App State never finish execution

Dear UiPathers

I have a problem when using the activity “Check App State”.

In my process, when I am running it, I have a nested “Check App State”. The first one is executed and finishes within 5 seconds (I put a delay on 5 seconds). The other one, which also checks an app state (Checks whether or not a GUI element is present) also has a delay on 5 seconds, however, that activity is being executed and ends after a whole 5 min?! How come this is the case? I have linked the part of my process where you can see the nested “Check App State”.

Hope some bright minds might shine some light into why one “Check App State” is quick and the other is very slow. Hope to hear from you.

Yours sincerely…
Genghiz. Khan

@nmjvk,

One thing you can check is Input–>Target properties:
image

Thanks,
Ashok :slight_smile:

Hi @nmjvk ,

In check app state activity, you can make use of the properties visibility check and wait for page load in order to take action as soon as the browser or element is loaded.

Also the default wait time itself is 5 seconds. Try leaving the field blank and use the above mentioned properties.

Please refer the url
Activities - Check App State.

Hope you get the solution.

Let me know if you need further assistance.

Thanks,
Gautham.

Dear Gautham

I just tried to follow your instructions, unfortunately it did not work. It still takes about 4-5 min for the check app state to be executed. Here is my property window:

Yours sincerely…
Genghiz. Khan

Hi @nmjvk ,

Please leave the timeout field empty and try.

Let me know if it still takes that much time.

Thanks,
Gautham.

Dear @Gautham_Pattabiraman

I left the timeout field empty and it is still taking those 4 min approximately to check app state. Do you have any other suggestions? I can find any other posts on UiPath Forum which have this error as me.

Yours sincerely…
Genghiz. Khan

Hi @nmjvk,

I see in your screenshot you have the ‘Wait for page load’ setting set to ‘NWaitForReady.Complete’

Please try using ‘NWaitForReady.Interactive’ or even ‘NWaitForReady.None’ with a hardcoded delay.

It may be that your application is very slow to ‘completely’ load, and your timeout countdown only starts once the page is fully loaded?

May be worth experimenting with the ‘Responsive websites’ setting as well depending on what it is that you are automating.

Hope this helps!
Please mark as answer if it does.

Happy Automation!