in the same activity i just modified max no fo result: 50 ( some known value less than actual count ) and printed the count value through the same argument.
this time i got the output
Something goes wrong with the scrapping, the output datatable is not instanciated correctly but this happens silently. The complains arise when the datatable is exploited later and not found.
With the “error on”, the issue appears on the spot.
@Fresher
Can you try your to redo your activity but by selecting the elements you need (and not use the “get whole table” choice)?
I just look back at my (old) workflow and the number of max result was at 0, my link selector was the same as you but both the target selector and the ExtractMetada were more precise.
Am not sure where and what am missing - also am feeling hard to explain because the same workflow runs and provide the output as variable, but not as argument.
i tried multiple times with different version - but same happening for all