Skip to content

429 exception handling for serial ingestion flow

Ankur Rawat requested to merge ankurrawat/429HandlingInSerialIngestion into azure/m23-master

What is the issue or story related to the change?

Currently when we call create record API with <50 records in the request and if cosmosDB is experiencing heavy load and throttling requests then cosmosDB 429 exception is returned as 500 from the service. Made the changes to return 429 as it is to user through Global exception handler.

Merge request reports