Hi there @zeshanm9,
I have gone through your workflow and sometimes it might miss some pages but still dispatch your queue item without throwing error because you have kept the ‘Continue on error’ property as true.
Secondly, if you are using 2019.5 then maybe use ‘Bulk add queue items’ it will push the whole data table, no need to check so many conditions I surmise.
Again, after all queue items are dispatched for the first page use a clear data table activity just for safety.
By the way I see in the following selector of yours : (see quoted text)
<webctrl css-selector='body>app-dashboard>main>div>app-parcelserviceworkspace>div>div>div>div>div>p-datatable>div>p-paginator>div>a>span' idx='3' isleaf='1' tag='SPAN' />
you have an ‘idx’ attribute that might be changing - so stabilize the selector. Keep wait for ready as interactive and give time-outMS as much as you need for it load.
If your data has table tag - then it will offer you to extract the whole table - if not then data scraping wizard has to be used.
One more thing - sometimes the ‘next’ button or the element that indicated the next page navigation might not remain in the same DOMXpath so better to run the same data scraping wizard/activity untill the ‘next page’ element exists int he pagination.
Hope all these tips help