I’m using SuiteQL through REST with the limit and offset parameter and noticing that some results are returned duplicated across pages, while other rows that should be in the response are missing. What could the issue be?

AI generated answer (using internal Slack threads):

The issue you're experiencing with SuiteQL through REST with the limit and offset parameter, where some results are returned duplicated across pages, while other rows that should be in the response are missing, could be due to the way NetSuite handles pagination and sorting of the results. When you use the

limit

and

offset

parameters in SuiteQL, NetSuite returns a specific number of records starting from a certain point in the dataset. However, if the data in the database is being updated while you're fetching the results, it could lead to inconsistencies in the returned data. This is because the offset is applied after the data is fetched but before it is returned, so if the data changes between fetches, the offset could point to a different set of data. To avoid this, you could try the following: 1. Sort your data by a unique, unchanging field, such as the internal ID or creation date. This will ensure that the order of the data remains consistent across fetches. 2. Fetch the data in smaller chunks. This will reduce the time between fetches and thus reduce the chance of the data changing in between. 3. If possible, fetch the data during a time when updates to the database are less likely to occur. Remember, these are just possible solutions and may not completely eliminate the issue. The best solution would depend on your specific use case and the nature of your data. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******