Click generic error is something that hasn’t been a good experience in my projects too.
These are the solutions that have worked for us.
- Keep continue on error as ‘True’ if the activity is happening but also throwing an error.
- Keep a separate try catch block and see whether the subsequent element exists and then retry.
- Have a stable selector and use Click image activity if all the environment resolutions is the same.
- Use a reliable selector which does not change and better to not be a minimalist when setting attributes for the selector.
These are the things that I follow and I haven’t faced any issues yet. Hope it helps
PS: Do not keep the loading as ‘INTERACTIVE’ rather keep it as ‘COMPLETE’ and also use both TimeoutMS and if and only if required use a configurable hardcoded delay before and after.
Even after this this issue exists then maybe throwing an exception and moving on might be the only thing to go about it.