Troubleshooting
What some of the messages you might see across Agile Gauge's views actually mean.
"Couldn't reach Azure DevOps"
A network problem prevented Agile Gauge from loading data for this view. Check your connection and try again. A related message, "you don't have access to this data," means your Azure DevOps access level doesn't currently permit reading what that view needs, rather than a connection problem.
An empty sprint
"This sprint is empty" is a real, complete answer, not an error — it means the sprint genuinely has no committed items, and Agile Gauge shows that plainly rather than treating it as a failure.
No active sprint / dates look wrong
If a view falls back to showing the most recently finished sprint instead of a currently running one, the most common cause is the team's iteration dates in Azure DevOps: check the team's iteration dates in Project Settings to confirm a sprint is genuinely marked as running for today's date.
Missing history / estimated figures
If a note says Azure DevOps didn't return the change history for one or more work items, their time in each stage is estimated rather than measured precisely — this happens when Azure DevOps' own history for that specific item couldn't be read. The item is still counted in the figures; this is a precision note, not a sign that data was lost.
Numbers look empty or wrong on first use
By far the most common cause is workflow mapping — if your team's states aren't yet mapped to Agile Gauge's stages, items can be counted as "not started" even though real work is happening. Check Configuration → Workflow Mapping first.
Most views disclose exactly what went wrong (a partial read, an unavailable setting, a missing baseline) inline, right where the affected figure would otherwise be — read the note next to a suspicious-looking number before assuming it's simply incorrect.
See Support for how to get help, and what to include so we can help you faster — since Agile Gauge reads only from your own organization, in your own browser, we don't have a copy of your data to look at on our end.