batchSize" issue

I would suggest updating to the modern Paging Grid - it is far more flexible and has better error handling (in general) when a data set has unexpected properties.  It looks in your case like you've passed a Paging Info variable with a batch size of 10, but then passed (perhaps the incorrect) data set with 17 rows, which breaks the grid.  If you're using a View, you might also want to ensure the column indicated in the CDT as being the "primary key" does not have duplicates across ANY number of rows, as even the modern paging grid displays a similar-looking error if it sees the same primary key used across multiple rows.

I would suggest updating to the modern Paging Grid - it is far more flexible and has better error handling (in general) when a data set has unexpected properties.  It looks in your case like you've passed a Paging Info variable with a batch size of 10, but then passed (perhaps the incorrect) data set with 17 rows, which breaks the grid.  If you're using a View, you might also want to ensure the column indicated in the CDT as being the "primary key" does not have duplicates across ANY number of rows, as even the modern paging grid displays a similar-looking error if it sees the same primary key used across multiple rows.