Has anyone else had trouble with SuiteQL where if you have too many rows in the pagination - records end up being dropped? Background: We load all transactions for a given posting period, then recursively run subsequent queries to get TransactionLine and TransactionAccountingLine - when I set the number of transactions to be retrieved in the TransactionLine and TransactionAccountingLine to be 500 distinct transaction headers - I get incomplete results (with 0 errors). Lowering to 100 distinct transaction headers yields the correct results.

I was gonna say errors with retrieval due to hammering the API, but if you say 0 errors, then that is odd. I got errors previously but because my pagination code was returning the data as-is after the first error; which resulted in truncation.

Ya - we capture the 429 errors for running too fast - but its simply missing records that show up when we chunk the

where

clause into 100, rather than 500, selections