I’ll try to explain it in more detail, please tell me if I need to explain further.
The CV Scope has latest image cached inside (let’s say Image1, made on Screen CV Element Exists).
Step 1. It goes to the next activity: CV Element Exists → WIth Screen CV Element Exists.
It checks if the last cache is made on the same screen → It is, do NOT refresh
(Cache is still Image1, made on Screen CV Element Exists)
Step 2. It goes to the next activity: CV Click → With Screen CV Click
It checks if the last cache is made on the screen → It is NOT, it REFRESHES
(Cache is now Image2, made on Screen CV Click)
Now it loops all over. It goes to Step 1 and because the cache screen vs activity screen differ, it refreshes and we have Image 3. And Step 2 refreshes again.. and so on and so on
If both activities had the same screen the refresh is not triggered as we the cache screen matches the current activity screen
Separately, regarding if it exists or not
Somebody else said it in the topic, so I’ll confirm it.
The activity CV element exists terminates if the element exists so it only waits for 1. First appearance or 2. Timeout and element has not been found
We have another activity in the Modern experience (Check App State) that can be used with ComputerVision targeting that has more controls like: Wait For Element to appears, Wait for element to dissapear. Most of the modern experience activities can be used with CV targeting. The ability to scroll to cv element is not yet in the modern experience.