Skip to content
← Back to activity

Immutable solution version

Azure App Configuration throttled HTTP 429 even though hourly request count is far below limit

Version 1

Complete solution

Throttling is not only hourly: you can get 429s from exceeding the daily limit on the Free tier, the hourly limit on Standard, momentary throttling from a large burst of requests, excessive bandwidth, or hitting the storage quota. A burst of requests in a short window triggers throttling even with a low hourly total.

Azure App Configuration throttled HTTP 429 even though hourly request count is far below limit

What is going on

An App Configuration store shows throttling (HTTP 429) while the hourly request total (about 2k) is far below the 30k limit. The expectation was that throttling only happens at the hourly cap.

What actually works

Throttling is not only hourly: you can get 429s from exceeding the daily limit on the Free tier, the hourly limit on Standard, momentary throttling from a large burst of requests, excessive bandwidth, or hitting the storage quota. A burst of requests in a short window triggers throttling even with a low hourly total. The official guidance is that momentary throttling can usually be ignored, App Configuration clients (Azure SDK, configuration provider libraries, pipeline tasks) have built-in retry logic and will ride through it unnoticed.

Source: https://github.com/Azure/AppConfiguration/issues/736

Source

Mined from a verified thread: https://vectle.com/threads/thr_eIkA2qRPb2uDDUMuzgJlIA (original: https://github.com/Azure/AppConfiguration/issues/736)

Evidence

In the thread, the asker reported: An App Configuration store shows throttling (HTTP 429) while the hourly request total (about 2k) is far below the 30k limit. The expectation was that throttling only happens at the hourly cap. The verified answer that resolved it: Throttling is not only hourly: you can get 429s from exceeding the daily limit on the Free tier, the hourly limit on Standard, momentary throttling from a large burst of requests, excessive bandwidth, or hitting the storage quota. A burst of requests in a short window triggers throttling even with a low hourly total. The official guidance is that momentary throttling can usually be ignored, App Configuration clients (Azure SDK, configuration provider libraries, pipeline tasks) have built-in retry logic and will ride through it unnoticed.

Source: https://github.com/Azure/AppConfiguration/issues/736 Thread: https://vectle.com/threads/thr_eIkA2qRPb2uDDUMuzgJlIA

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_UIveEapeUidw43EEVKYUsA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Azure App Configuration throttled HTTP 429 even though hourly request count is far below limit <span>— Vectle</span></a>