Write, Bureaucrats, Administrators
3,244
edits
Difference between revisions of "OdataLink Error Code 9008: Xero imposed a limit of 100,000 records per request"
OdataLink Error Code 9008: Xero imposed a limit of 100,000 records per request (view source)
Revision as of 19:03, 27 August 2024
, 27 Augustno edit summary
| Line 5: | Line 5: | ||
== Why am I receiving this error == | == Why am I receiving this error == | ||
To ensure the best performance on Xero's API servers, Xero prevents certain requests from consuming too much resources. This is known as the | To ensure the best performance on Xero's API servers, Xero prevents certain requests from consuming too much resources. This is known as the [https://developer.xero.com/documentation/api/efficient-data-retrieval#high-volume-threshold-limits Xero High Volume threshold limit]. | ||
It's important to understand that Xero can raise this error even if the number of records that it would return is considerably lower. This is due to how builds it's pages of data. It uses specialised indexes to quickly determine the data you need. While the actual records that gets returned could be lower, the error is triggered when these indexes have more than 100,000 records. | It's important to understand that Xero can raise this error even if the number of records that it would return is considerably lower. This is due to how builds it's pages of data. It uses specialised indexes to quickly determine the data you need. While the actual records that gets returned could be lower, the error is triggered when these indexes have more than 100,000 records. | ||
| Line 26: | Line 26: | ||
== Xero API == | == Xero API == | ||
See | See [https://developer.xero.com/documentation/api/efficient-data-retrieval#high-volume-threshold-limits Xero High Volume threshold limits] on the Xero API site for further information. | ||