Hi @Anil_G ,
Thank you for your response.
Adding each activity into retry scope(I’m assuming that is what you are referring to here) isn’t the best way to go about addressing this issue as it increases the dev effort as well as makes the workflow bulky.
Also, the retry scope requires us to pass in a condition i.e it will go on retrying as long as the condition is not met.
If you were referring to the retry present within the modern activities, then that too requires a validation to be set and it again, increases the dev effort.
I was looking for a simpler way to address this issue, but it seems like this can’t be resolved easily.
As for checking the selectors, I did find that the aria-disabled property
is set to true when its disabled, and we could use that but then again adding this check to 40-60 UI Activities translates into additional 25+ Get Attribute Activities to check its state before interacting with it.
I’d also like to optimise the process while I’m at it, but I guess I’m getting a little too greedy with this hehehe
I appreciate your response thought, thank you for the suggestions. I hope UiPath looks into this and comes up with a neater resolution for it.
Kind Regards,
Ashwin A.K