We are also facing the same challenge as explained in this post (in multiple solutions).
While interrogating: when our Universal Web Adapter (UWA)(Chrome) is navigating from one page to another, the previous page stays matched. The only way to get the current page matched, is by doing a rematch on the previous page (which then unmatches) whereafter we also have to execute a rematch on the current page (which then matches). We have tried different match rules, but it doesn't seem to make a difference.
While building a flow: as a consequence of this issue, we have to constantly use the rematch method in our flows. If we don't, we will get an error, because the control isn't matched.
Is there any way to solve this? Or is there any work-around? Our current version 19.1.49.
@RobinT51 I think this has more to do with the page and the match rules you have chosen than the UWA in general. If the page itself isn't navigating, then it would make sense that you'd have to rematch as everything is on one page. If it is truly multiple pages (i.e. you see the page refresh during navigation and the URL changes), then it might be that you have match rules that are too loose and allow for multiple pages to match the same control. Is the page you are accessing publicly accessible? If so, I could take a look and see how I would match it. If not, you might open a support request as you might just need some hands-on assistance to look at your specific pages.