429 - woah, that's a lot of requests in https://marketplace.visualstudio.com/

Hi @sri kanth ,

The 429 – "Woah, that's a lot of requests" page means the Marketplace service is rate‑limiting your identity (usually shown as Request was blocked due to exceeding usage of resource 'Concurrency' in namespace 'VSID'). Clearing browser cache won't help, because the block is on the account/identity side, not in the browser.

A few things to check first:

• Stop any automation that publishes or signs in repeatedly. CI/CD pipelines (for example GitHub Actions triggered by pull requests or Dependabot) can run several vsce publish jobs in parallel with the same publisher token and keep the block active. Add a concurrency lock or limit publishing to manual/release triggers.
• Avoid frequent retries. Each retry can extend the throttle window.
• Try once from a clean browser profile and a different network, only to rule out a stuck session or proxy.

If it still fails after that, this needs the Visual Studio Marketplace team to look at your account, since publisher and account‑level blocks can't be inspected or cleared from here. You can reach them at VSMarketplace@microsoft.com or open an issue at https://github.com/microsoft/vsmarketplace/issues.

For background on how throttling works, see https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/rate-limits?view=azure-devops

If you get a new error after trying the above, share it and I'll take another look.If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback.

Thank you.

A 429 response means the Visual Studio Marketplace is actively rate‑limiting your publishing attempts, usually because your account, IP address, or automated workflow is sending repeated or high‑frequency requests that the system interprets as excessive. This can happen if a CI/CD pipeline keeps retrying failed uploads, if a corrupted .vsix package triggers repeated submission attempts, or if an outdated PAT or OAuth token is stuck in a loop. Once Marketplace throttles you, the block can persist indefinitely until the underlying request pattern changes. Because the error has lasted this long, the most effective steps are to regenerate your PAT, temporarily publish from a different network to bypass IP‑level throttling, ensure no automated process is hammering the Marketplace API, and if the issue continues contact Microsoft support so they can check whether your account or IP has been flagged by Marketplace rate‑limit protections.