Since the result table’s UI selectors are highly dynamic, I cannot use a Check App State directly on it. Instead, I use it on the “Search” button to detect when it reappears, assuming that means the table has loaded.
This approach has been working perfectly for months with all three accounts. However, recently, for one specific account, the Check App State fails in unattended mode but works fine in attended mode.
I even tried adding another Check App State inside the existing one for the same element, which initially worked, but now even that doesn’t. There have been no changes to the website, UI selectors, or elements.
I’m using UiPath 2022.10.5. Has anyone encountered a similar issue? Any insights on why this might be happening or possible solutions would be greatly appreciated!
While developing, the loading screen disappeared too fast, so I couldn’t use a Check App State with Element Disappears for it.
I even tried using a classic activity, but that didn’t help either. Even when the loading screen was still there, it kept saying the “Search” button had already appeared. So, classic activities are pretty much out of the question here.
So here the functionality what you are trying is worked earlier but now it was not working right?
did you tried by re indicating the same element before changing logic of your code.
even if its not worked then try to estimate how much time it is taking and in properties pass some time in timeout section and enable wait for page load as complete
Re-indicating the element hasn’t worked so far, and I can’t use the Wait for Page Load activity since the page itself doesn’t refresh—only the component inside updates asynchronously.
one thing i want to let you know that Wait for page load is not activity, in check app state there is properties section in that under the target you are able to see wait for page load property will be there, modify that as complete or interactive. give a try with both and see
If I switch to CV, it might not work for the other selectors since Check App State is already working fine for them. Plus, even in this case, when I nested the Check App State, it was actually working before.
I can’t fully rely on CV here, as it might introduce inconsistencies with the existing selectors.
normally in this scenario…we need to indicate the search button before load and after load and check if there are any differences in selector
then table even if it is dynamic try to target the first row first column value or a header value which might come and try waiting for that
alternately use two check app states one for the loading icon to appear and other for disappear and if it does not appear then the assumption would be it is already loaded and if appeared it would disappear anyways after load
@Anil_G
I didn’t use this approach exactly, but it gave me an idea. In UiPath, I used the Object Repository, where I had two objects—one for clicking the search button and another for checking if the page was loaded (Check App State). Instead of using the object meant for checking if the page was loaded, I used the object for clicking the search button in the Check App State activity.
This now works perfectly. Thanks for all the help!
