A blip in the connection can no longer cost you your settings
When Azure DevOps briefly failed to return your saved settings, the hub used to treat that exactly like you had never configured anything: it showed the built-in defaults, and the next automatic save, for example remembering which team you had open, quietly wrote those defaults over your real settings. The same could happen to your organisation’s workflow mapping. The hub now tells the two cases apart. When it cannot read a document, it works from a temporary stand-in instead of the real one, never saves over what you actually have, and checks again a short while later. If you try to save while this is happening, the hub says so plainly, in your language, so you know nothing was lost and can try again. The rest of the time, nothing changes: settings load, save and refresh exactly as before.
Views say so when a mapping could not be loaded, and stop asking you to set up one you already have
Every view that depends on your workflow mapping now shows a short notice when that mapping could not be loaded, and works from the built-in defaults only until the read recovers, rather than quietly showing default-based figures as if they were yours. An unreadable mapping is also no longer mistaken for a missing one. Before, a brief connection problem could replace an analytics view with a setup screen asking you to configure a mapping you already have. The setup check and the readiness report now say plainly that they could not check, instead of asking you to add a mapping that already exists, and the views themselves stay available while the read is retried.
Dashboard customization actually customizes now
Showing or hiding a widget on your dashboard no longer moves it, and moving one widget no longer switches on every other optional widget along with it. The drag handle now behaves like one. None of this touched Restore classic layout, which works exactly as it did before.
The last language inconsistencies, cleared up
A few labels on Sprint Summary, including Download All and Refresh, stayed in English regardless of your chosen language. They now follow it like the rest of the view. Portuguese copy across the product is consistent throughout, so wording no longer shifts between two dialects depending on where you are reading it.
Updating
Azure DevOps updates the extension automatically, nothing to install. Everything above works with your data staying inside your Azure DevOps organisation: no PAT, no data sent to us. If a setting still looks wrong after the update, use Ask Henry in the top bar and a real person replies within one business day.
Related: Service status