Good day. I would like to know if there’s any way to make the Element Exists activity faster in checking the UI element? Because it’s taking too long for it to check and I couldn’t find anything in its properties also and in UIExplorer, there’s no setting in changing its speed.
The “Element Exists” activity in UiPath is designed to wait until the specified UI element exists or until a timeout is reached. If the element typically appears quickly, you can reduce the timeout to a lower value.
“OnElementAppear” event in combination with the “Wait For Ready” property set to “COMPLETE”. This can allow the automation to continue as soon as the element appears, rather than waiting for the entire timeout period.
No check app state and element exists are two different things
In UiPath, the “Check App State” activity is used to determine the state of a specified application or window. It allows you to check whether an application is running, not running, or in a specific state. This activity is particularly useful when you need to interact with applications in a controlled manner based on their current state.
Whereas The “CV Element Exists” activity is based on image recognition and can locate elements based on their appearance, even if traditional selectors are not available.
I’m currently using an application, not website, on checking the popup after clicking a button. Would it be okay if I only target the pop-up for Check App State to check?
The default time out for the element exist activity is 30000 milliseconds means 30seconds. You can change default time out in the Project settings. Then it will wait for the time what we will give.
Steps → Open the Project Panel → Click on settings → one window will open → In Left We have Activities settings, Click on the Ui Automation Classic → In that you have the Element exist option as shown below you can change the Timeout value in Run value and debug value.
If the element is not found, the ‘Element Exists’ activity searches for it until its default TIMEOUT of around 30 seconds. After this period, it throws an error.
Try this solution:
reduce even that TIMEOUT property value of the ‘Element Exists’ activity. to mention 10000 milliseconds.