PingOne synchronization limitations

PingOne can return errors when synchronizing with PingDataSync because of a rate-limiting mechanism in PingOne. A workaround for this issue has been implemented in PingDataSync.

The PingOne API contains a resource-limit 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 a large number of threads are in use.

If the PingDataSync server receives HTTP 429 errors from PingOne, it waits briefly and retries any failed operations again. An operation is retried up to 15 times to attempt to synchronize a change. This retry mechanism allows the PingDataSync server to process a change without the operation dropping as a failure after initial HTTP 429 errors.