Hi folks,
We have identified a data discrepancy issue where the ServiceNow Table API intermittently returns fewer records than expected when multiple API calls are executed in parallel. The occurrence is entirely random with no noticeable patterns observed either in the offset where the data loss happened or in the number of records.
For example, a request for 500 records may only yield 472 records. Because the API returns no error or exception, the data stream is being silently truncated. Our implementation appends offset and limit parameters to the Table API to fetch the required datasets, and the records are read sequentially in a streaming fashion using Gson's JsonReader object.
We are seeking a deeper understanding of why this occurs, as well as any official ServiceNow documentation describing this issue or its potential resolution. A similar behavior has been documented in the community thread: Table REST API returns duplicates / inconsistent data sets but a definitive root cause has not yet been identified.
Thanks,
Sanchit
