Thanks for the explanation! It can be used instead of Check App State to check that the next page appears or in your experience, for now Check App State is more reliable? I use Check App State almost in every workflow and it seems quite similar to using the Verify
I especially like the retry mechanism in this method. I know that can be done in a number of ways, but knowing that Self Healing robots in the future will specifically take advantage of Verify Execution makes me think that this is the way to go.
Awesome video and something I will definitely use going forward. Keep up the great work !!
Thanks a lot, much appreciated :-)
Thanks Jeppe, for this lovely video explaining verify execution!
I am so used to using old activities that I didn't even know about this. Very cool!
@@SrdjanS_Automations I think a lot of us still fall back on classic activities sometimes. Old love never dies 😄
Well done. Good reflexes with deleting the last letter 😁
🥷😄
Thank you ! Very appreciated video
....and a very appreciated comment. Thank you :-)
Great explanation. Crystal clear. Appreciate it!!
Thanks 🙏
Thanks for the video. Love that you explain how it works in the background.
You're welcome, glad you found it helpful :-)
good one, this saves a few problems with my automations :) I always used retry-scope to ensure if an expected element or screen appears - thanks
Hey, there are sooo many ways to solve any problem, right? :-) ...and thanks for the kind words. Means a lot.
thank u very much
You're very welcome :-)
Thanks for the explanation! It can be used instead of Check App State to check that the next page appears or in your experience, for now Check App State is more reliable? I use Check App State almost in every workflow and it seems quite similar to using the Verify
I especially like the retry mechanism in this method. I know that can be done in a number of ways, but knowing that Self Healing robots in the future will specifically take advantage of Verify Execution makes me think that this is the way to go.