Yes your understanding is correct, surface automation should be WYSIWYG. Obviously it's hard for me to diagnose from here, but here are a few more 'sanity' checks to try. Apologies if they seem dumb!
- In the wait stage, check it's definitely the region and not the parent Win32 element being used for the check exists condition.
- Check it's the right region element in the wait stage and not some other with the same name
- Add a navigate stage to execute the verify action with the highlight input set to True. This should show you where the app modeller thinks the region is at run time.
- Verify/highlight the parent Win32 element at runtime.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------