Im opening the website by open application browser activity in UiPath studio, but currently the website which i opening is server down and it is not even opening in the browser. I have used take screenshot activity for some screens in the website. As the website is not openned, but my workflow is trying to take the screenshot and fails there. What I need to do is, I need to tract whether the website opened or not then only all the activitied i kept inside the application browser activity need to be executed. Can anyone let me know how to achive this ?
Use check app state activity to check any Ui element which appears when the website works normally.
Another approach will be using get attribute activity to get the browser attribute which can indicate you the website opened normally or not. You can check the reliable attributes to use by Ui Explorer.
Which attribute in get attrivute activity should i use?
You can try readyState
Ready state will be 1 if website loaded. If failed with will return 0
Instead of take screenshot of website..use stake screenshot without any selector then it would take screenshot of whole screen ..so you have a trace
alternately enabling recording in orchestrator also will help in checking what is happening
cheers
Okey, Let me try this approch.Thanks
1 Like
Open Application/Browser → use Try Catch
Inside Try keep your normal UI steps (including Take Screenshot of the page).
When the site is down, the browser will still open and show a server error page (404 / server down).
In Catch (or after Open Browser with timeout)
Use Take Screenshot
Hai, I have tried this get attribute with ready state in retry scope with continue retrying on the error if the browser state is in “loading”. But still the UiPath workflow goes to the activitied inside the open browser activity and it is not stopping the workflow even the site is not get loaded. Is there any other way to use this get attribute methode in UiPath to check whether the site is loaded or nor and if not the workflow should be stopped after the maximum retry limit exceeds.
You should use Check App State. It’s what it’s designed for.