@Iqr
you can split:
For login: Attach browser waiting for the login form Retry scope 1
Enter login credentials
Element exists if browser is still on login page (I assume e.g. an error message or anything else)
If not then use second retry scope for synchronizing with the Home page
wrapping retry scope into a try catch is not advisable as it is equalizing the exceptions and does loose the differentation.
What we did often was setting up a custom retry scope:
- for each activity with Enumerable.Range(1,NoOfRetries).toList
- implementing the custom condition check and using break activity for ending the loop
- delay activity
- optional: throwing error