Azure DevOps Deployment Groups stuck loading – ReactRootAdapter.js returns 404 BlobNotFound

Aaron 0 Reputation points
2026-11-06T10:05:52.67+00:00

Issue description

We are experiencing an issue with Azure DevOps Services where the Pipelines → Deployment groups page remains indefinitely on "Loading..." and never displays the deployment groups.

Our Azure DevOps organisation is hosted in West Europe.

Browser errors

Using browser Developer Tools, we identified the following JavaScript resource failing to load:

https://cdn.vsassets.io/v/M280_20261026.4/_scripts/TFS/min/VSS/ReactRootAdapter.js

The request returns:

  • HTTP Status: 404 Not Found

Error Code: BlobNotFound

Error Message: The specified blob does not exist.

The browser console also reports:

Script error for "VSS/ReactRootAdapter"

Troubleshooting performed

Tested using Google Chrome and Microsoft Edge InPrivate.

Reproduced the issue after disabling the browser cache.

Tested the JavaScript resource directly from our corporate internet connection.

Repeated the test using an independent LTE connection.

Repeated the test using mobile data.

The same BlobNotFound response was received across the different networks.

Assessment

The CDN endpoint is reachable, but the requested JavaScript resource returns 404. This suggests a missing or incorrectly referenced frontend asset rather than a local firewall or connectivity issue.

We have not made changes to our deployment agents or deployment groups.

Assistance requested

Could the Azure DevOps engineering team please investigate whether the referenced JavaScript resource is missing from the Azure DevOps CDN deployment?

We would also appreciate confirmation of whether this is a known issue affecting the Deployment Groups interface and whether a workaround is available.

Thank you.Issue description

We are experiencing an issue with Azure DevOps Services where the Pipelines → Deployment groups page remains indefinitely on "Loading..." and never displays the deployment groups.

Our Azure DevOps organisation is hosted in West Europe.

Browser errors

Using browser Developer Tools, we identified the following JavaScript resource failing to load:

https://cdn.vsassets.io/v/M280_20261026.4/_scripts/TFS/min/VSS/ReactRootAdapter.js

The request returns:

HTTP Status: 404 Not Found

Error Code: BlobNotFound

Error Message: The specified blob does not exist.

The browser console also reports:

Script error for "VSS/ReactRootAdapter"

Troubleshooting performed

Tested using Google Chrome and Microsoft Edge InPrivate.

Reproduced the issue after disabling the browser cache.

Tested the JavaScript resource directly from our corporate internet connection.

Repeated the test using an independent LTE connection.

Repeated the test using mobile data.

The same BlobNotFound response was received across the different networks.

Assessment

The CDN endpoint is reachable, but the requested JavaScript resource returns 404. This suggests a missing or incorrectly referenced frontend asset rather than a local firewall or connectivity issue.

We have not made changes to our deployment agents or deployment groups.

Assistance requested

Could the Azure DevOps engineering team please investigate whether the referenced JavaScript resource is missing from the Azure DevOps CDN deployment?

We would also appreciate confirmation of whether this is a known issue affecting the Deployment Groups interface and whether a workaround is available.

Thank you.

Azure DevOps
0 comments No comments

1 answer

Sort by: Oldest
  1. Aaron 0 Reputation points
    2026-11-06T10:09:16.02+00:00

    We have confirmed that the issue persists across multiple browsers and independent internet connections.

    The missing ReactRootAdapter.js resource consistently returns HTTP 404 with BlobNotFound from Microsoft's Azure DevOps CDN.

    Unfortunately, our Azure subscription only has Basic Support, and the Developer Community sign-in process is currently returning HTTP 400, preventing us from using that escalation channel.

    Could a Microsoft moderator please help escalate this to the Azure DevOps engineering team or advise on an alternative method of reporting this suspected service-side defect?

    The Deployment Groups interface remains inaccessible.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.