Azure DevOps VS40317 error persisting for several days

Question

Azure DevOps VS40317 error persisting for several days

Strydom, Teresa 0

Error for all Widgets on our ADO projects due to VS40317 error. We have tried various browsers and forced resets.

kagiyama yutaka 5,575 Reputation points

2026-10-05T10:56:09.17+00:00

Could you share the full VS40317 error message from one of the affected widgets, with any sensitive details removed? Does the same error occur for every user, or only for specific users? That should help narrow down where the failure is occurring.

2 answers

Your answer

kagiyama yutaka 5,575 Reputation points

2026-10-05T10:56:09.17+00:00

Could you share the full VS40317 error message from one of the affected widgets, with any sensitive details removed? Does the same error occur for every user, or only for specific users? That should help narrow down where the failure is occurring.

Answer 1

kagiyama yutaka 5,575

I think this needs checking beyond the browser. VS40317 alone doesn't identify the cause.

Since widgets fail across projects, check built-in vs Marketplace widgets. F12 → Network → reload the dashboard. Capture the failed request, HTTP status, full error and UTC time. If using Azure DevOps Services, check service status for your geography. If it persists, send the details and HAR to Azure DevOps Support securely. HARs may contain tokens.

0 comments

Answer 2

For Azure DevOps widget failures persisting across browsers and resets, use this troubleshooting path:

Verify the organization URL format. Use the current format: https://dev.azure.com/{organizationName}. A legacy URL configuration has been associated with intermittent Azure DevOps loading issues in a similar case.
Fully sign out and clear browser state.
- Go to https://aka.ms/VsSignout
- Clear browser data with Ctrl+Shift+Delete
- Remove cookies and site data, cached images and files, and autofill form data
- Clear Microsoft Edge data as well, because Visual Studio IDE uses Microsoft Edge cookies
- Close all browser and Visual Studio instances
Test in a private browsing session. Open an InPrivate or incognito window and try the affected Azure DevOps project again.
Confirm the correct account identity is being used. If multiple identities exist, sign in again and choose the correct account type and identity.
Check for network interference.
- Test from a different network or personal device
- Verify any corporate proxy allows *.visualstudio.com and *.azure.com
- Ensure the firewall allows HTTPS traffic to Azure DevOps endpoints
- If a VPN is in use, test with the VPN disabled
If the issue is only in Visual Studio, reset the IDE connection.
- In Team Explorer, remove all Azure DevOps connections
- Delete cached credentials from Windows Credential Manager
- Restart Visual Studio
- Add the Azure DevOps connection again
If the issue continues after several days, collect diagnostics and open a support request. The documented next step is to create a browser trace of the failed sign-in or load attempt, then create a Microsoft Support request including:
- a detailed issue description
- steps already attempted
- browser trace files
- screenshots of the error