This is indicating that the Next Data page selector isn’t captured correctly with Fuzzy or Strict Selector but it’s working on Fallback selector that is Computer Vision and it’s slowest one.
Here is sample code with correct selectors.
ExtractTable.xaml (16.3 KB)
Output:
Thanks,
Ashok ![]()
I have the same problem.
But I have one more doubt, because in my case when it reaches the last page, instead of finishing the process, it goes back 2 pages, and extracts the same elements again. Shouldn’t it stop data extraction when the “next page” icon disappears?

