2025-01 api version returns 200 instead of 429

HI There,

We are getting 200 status code with 2025-01 instead of 429 in an event where the complexity budget is exhausted. See the picture below.

The 2024-10 version correctly returns 429 error code with Retry-After header.

Can you please fix this?

Thanks

Welcome to the community!

Thanks for reporting this. Our team released a hotfix earlier today to fix this. Here’s the changelog post!

Let us know if you have any other questions.

Best,
Rachel

Sign up