VS Code Marketplace extensions return 404 after successful vsce publish; publisher hit VSID Concurrency rate limit

Hello Visual Studio Marketplace Support team,

We need help checking the status of our Visual Studio Marketplace publisher and two VS Code extensions. After a GitHub Actions release workflow reported a successful vsce publish for version 0.15.1, the public Marketplace item pages still return 404, and a later retry was blocked by a Visual Studio Marketplace / Azure DevOps rate limit.

Publisher information:

• Publisher ID: devsessioncanvas
• Publisher page: https://marketplace.visualstudio.com/publishers/devsessioncanvas

Extensions:

• devsessioncanvas.dev-session-canvas
  • Marketplace item URL: https://marketplace.visualstudio.com/items?itemName=devsessioncanvas.dev-session-canvas
• devsessioncanvas.dev-session-canvas-notifier
  • Marketplace item URL: https://marketplace.visualstudio.com/items?itemName=devsessioncanvas.dev-session-canvas-notifier

What happened:

1. We published version 0.15.1 through GitHub Actions.
2. The initial release workflow showed vsce publish succeeded, but our marketplace verification step later failed because the Marketplace item pages were not publicly visible.
3. Both extension item pages returned 404 when checked publicly.
4. A later retry failed during vsce publish for devsessioncanvas.dev-session-canvas-notifier with a RequestBlockedException caused by resource Concurrency in namespace VSID.
5. When opening Marketplace / Azure DevOps pages in the browser, we also saw a 429 page: 429 - Woah, that's a lot of requests.

Initial publish run:

• GitHub Actions run: https://github.com/ZY-WANG-0304/dev-session-canvas/actions/runs/27249950645
• Relevant observation: the workflow reported the package as published, but Marketplace visibility verification failed afterwards.

Retry run:

• GitHub Actions run: https://github.com/ZY-WANG-0304/dev-session-canvas/actions/runs/27365043421
• Failed command:

text

/home/runner/work/dev-session-canvas/dev-session-canvas/node_modules/.bin/vsce publish --packagePath /home/runner/work/dev-session-canvas/dev-session-canvas/extensions/vscode/dev-session-canvas-notifier/dev-session-canvas-notifier-0.15.1.vsix

• Error:

Publishing 'devsessioncanvas.dev-session-canvas-notifier v0.15.1'...
Error: {"$id":"1","innerException":null,"message":"Request was blocked due to exceeding usage of resource 'Concurrency' in namespace 'VSID'. For more information on why your request was blocked, see the topic \"Rate limits\" on the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=823950).","typeName":"Microsoft.TeamFoundation.Framework.Server.RequestBlockedException, Microsoft.TeamFoundation.Framework.Server","typeKey":"RequestBlockedException","errorCode":0,"eventId":3000}

Browser 429 evidence:

• Page message: 429 - Woah, that's a lot of requests
• Timestamp shown on page: 2026/6/11 16:41:51 (UTC)
• Request ID / correlation ID shown on page: 9ecac8b7-d9ad-42de-b6ad-9c37b7b1c77a

Could you please help us confirm the following?

1. Whether publisher devsessioncanvas is in good standing and allowed to publish VS Code extensions.
2. Whether either extension is hidden, unpublished, suspended, pending review, or blocked by policy.
3. Whether version 0.15.1 was actually accepted by Visual Studio Marketplace for the two extensions.
4. Why the public Marketplace item pages return 404 after vsce publish reported success.
5. Whether the VSID Concurrency rate limit can be cleared, or when it is safe for us to retry publishing.

We have stopped retrying publishes for now to avoid increasing the rate-limit pressure. Please let us know the recommended next step.

Thank you.