PingOne synchronization limitations
Learn about limitations when synchronizing with PingOne using PingDataSync.
Rate limiting
The PingOne API contains a rate-limiting mechanism to prevent clients from overwhelming the service and returns HTTP 429 error codes when this limit is reached. Because PingDataSync sends changes to a destination as quickly as possible, the server might hit this limit, especially if it’s using several threads.
If the PingDataSync server receives HTTP 429 errors from PingOne, it waits briefly and retries any failed operations up to 15 times. This retry mechanism allows the PingDataSync server to process a change without the operation dropping as a failure after receiving HTTP 429 errors.
Learn more about rate limiting in PingOne standard platform limits in the PingOne documentation.