How to fix 429 error for Azure Devops

Question

Issue summary Receiving HTTP 429 – “Woah, that’s a lot of requests” and being temporarily blocked due to exceeding rate thresholds.

User / Account

• [PII removed]

Error message observed

“You might be blocked due to the number of requests exceeding our rate threshold. View your usage page to see where your high usage is coming from. You will either need to reduce your usage below the threshold or try this request again later.”

Impact This block is preventing normal day‑to‑day work. Requests fail immediately once the threshold is hit, and the issue persists until the throttling window clears.

Context / When it happens

• Occurs during high‑frequency or bursty request patterns (e.g., repeated API or service calls in a short time window).
• The block appears tenant‑ or user‑scoped rather than a single request failure.
• The message explicitly references exceeding a rate threshold, consistent with HTTP 429 throttling behavior.

What I’ve checked so far

• Confirmed the error is a 429 (Too Many Requests) response.
• The service indicates usage must be reduced or allowed to cool down before retrying.
• No clear visibility into which specific calls are driving the spike beyond the generic “usage page” reference.Issue summary Receiving HTTP 429 – “Woah, that’s a lot of requests” and being temporarily blocked due to exceeding rate thresholds. User / Account
  • [PII removed] Error message observed

  “You might be blocked due to the number of requests exceeding our rate threshold. View your usage page to see where your high usage is coming from. You will either need to reduce your usage below the threshold or try this request again later.”

  Impact
  This block is preventing normal day‑to‑day work. Requests fail immediately once the threshold is hit, and the issue persists until the throttling window clears. Context / When it happens
  • Occurs during high‑frequency or bursty request patterns (e.g., repeated API or service calls in a short time window).
• The block appears tenant‑ or user‑scoped rather than a single request failure.
• The message explicitly references exceeding a rate threshold, consistent with HTTP 429 throttling behavior. What I’ve checked so far
  • Confirmed the error is a 429 (Too Many Requests) response.
  • The service indicates usage must be reduced or allowed to cool down before retrying.
  • No clear visibility into which specific calls are driving the spike beyond the generic “usage page” reference.

Answer 1

Hi @Sicong Liu ,

Thanks for reaching out to Microsoft Q&A.

Solution:

It started working after trying in new machine.

Analysis:

The rate limiting you’re seeing is expected behaviour and it is intentionally designed to prevent a single user or process from overwhelming the backend with too many or too expensive requests in a short period of time.

To understand what’s causing the spike, please check the Usage page. It provides a breakdown of how the load is being generated. In particular, you should look for:

• Commands with high TSTU values, which indicate operations that consume a large amount of backend resources.
• A large number of commands executed within a short time window, where the combined TSTU total becomes high.

It appears that there are continuous heavy clone and fetch operations being run on the DsMainDev repository. This could be due to an automation or script repeatedly performing these actions.

If there is an automation or process running on your side, we recommend reviewing and stopping or adjusting it to prevent the repeated operations. 

Hope this helps!

---

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.