Hello,
I’m confused what should i use between ‘Check App State’ and ‘On element appear’ if I want to wait for an element to appear and when that element appears then the next activity will run
Hello,
I’m confused what should i use between ‘Check App State’ and ‘On element appear’ if I want to wait for an element to appear and when that element appears then the next activity will run
@zahranabilafalenanda You can use either but it is preferable to use modern check app state activity
Now based on the time out given it will wait for element to appear
If page load do take more time
You can have this inside retry scope also
Check app state basically works as on element appear as well…its more a modern version of on element appear
You can use either…but better go with check app state as it is latest activity
Cheers
To decide between using Check App State
and On Element Appear
in UiPath, let’s analyze both functionalities based on their typical uses:
Check App State:
This is a modern activity designed to replace certain classic activities such as Element Exists
It allows you to check if an element is in a particular state (appears or does not appear) within a given timeout period.
If the element appears within the timeout duration, the workflow can proceed immediately. Otherwise, you can handle the absence of the element within the Target does not appear
section.
Example Use Case:
Ensuring a login page’s element appears before filling in credentials. If the element appears, the automation proceeds to the login step; otherwise, it might handle an alternate action.
On Element Appear:
This classic activity pauses the workflow until a specified element appears on the UI.
Once the element appears, the remaining activities within this scope are executed.
This is useful for synchronizing the automation flow dynamically based on when UI elements become available.
Example Use Case:
Waiting for a notification element to appear after clicking a button to ensure the action succeeded.
Analysis Based on Usage
Check App State
is more versatile and integrates well with modern automation needs, checking both the presence and absence of elements.
On Element Appear
is specifically for ensuring synchronization by waiting for a specific element to become available before proceeding.
Recommendation:
If you need to wait for an element to appear and then run the next activity:
Use Check App State
—it’s designed to be more robust and feature-rich, enabling better handling within modern automation workflows.
Check App State Features:
Check App State
works the same way as Element Exists
, has additional features, and is the modern activity that replaces Element Exists.
On Element Appear Limitations:
On Element Appear is a classic activity; by this point, you should be working in modern. The Check App State activity may function better for your needs.
LLM helped me to write this but it’s validated by me.
Thanks for answering. I tried using retry scope, should the ‘number of retries’ parameter be filled in? Previously, I left it empty but got an error, and when I filled it in, it worked correctly. Is it possible if i don’t want to fill it in because I don’t know when the process will finish until the element appears
Thanks for answering, but how do I fill in the timeout
parameter in check app state
if I don’t know exactly when the element appears because the element appears when the backend process is finished?
Based on application behaviour you can define no of retries
Without no of retries u can not use as it’s a required paramagnetic for this activity
What u can do is add wait time like 10 sec or more between retry attempts
You can have it as a sale rate flow or state
Where it will wait for one min or more time and then retry
Give it a maximum time you expecting your Ui Element will take. If the element appeared before that it will resume immediately. It will work like implicit delay.