Question

A console application uses the Dataverse Web API to synchronize thousands of records nightly. During peak runs, the service begins returning HTTP 429 responses and the sync fails partway. You must make the integration resilient to Dataverse service protection API limits with the least custom code. What should you do?

Accepted Answer

Read the Retry-After header returned with the 429 response and pause the specified number of seconds before resending the request.

Answer

Immediately resend each failed request in a tight loop until it succeeds, ignoring any response headers.

Answer

Add the header MSCRM.SuppressDuplicateDetection=true to every request so the limits no longer apply.

Answer

Switch every request to run inside a single $batch operation so the limits are counted only once per batch.