Hi Arun!
There is no direct trigger happening when the next page button is clicked (yet)- we rely on the query populating the table to detect the input of which page to load and re-run the query when that changes
Setting the query to run automatically when inputs change is the easy way to do this, but I see you are also passing in a searchTerm here. If you go to the advanced settings tab of the query, there is a "Watched Inputs" setting under the Advanced Options section. Can you add in searchLinksTable.paginationOffset as one of the selections there? That will cause the query to run whenever that value changes, while still maintaining the other "manually triggered" behaviors.
