It tests whether the returned container is nonempty. That's embarrassingly literal.

Nonempty failure, then, so your dashboard is successfully detecting that it received some stuff

Have the maintainer separate request success from the returned status value. Confirm the field meanings against that installed version before changing the display mapping.

Maintainer has the matching documentation now. Failure bypasses the status mapping in the revised parser.

What does the screen show instead, because a parser fix can still leave yesterday's reassuring colour sitting there?

I'd remove the current-status claim on failure. Keep the last successful reading separately if somebody genuinely needs it, with its age visible.

Liam, I'd keep it for diagnosis, otherwise every broken read erases the clue you were looking at just before it broke

Separately was the important bit. I don't want the old value wearing the current green label.

Hassan, the saved diagnostic history can retain it even if the live tile is unavailable. Those are different display choices; neither needs to discard the previous successful reply.

We're using an unavailable live tile and a separate last-success line with time. History remains intact.

Try the screen with updates stopping entirely too, not only a tidy failure reply reaching the parser.

That exposed a second bug: the age display only refreshed when replies arrived.

Ah. The clock that stops with the news.

Did the maintainer add an independent freshness check? Also try a failure before any successful read, so there isn't always an old value to display.

Yes. Freshness now advances independently, and startup failure says no successful reading rather than showing a default status.

Include an unexpected reply shape in the parser tests. It should not fall through to a plausible status while you wait for someone to explain the changed contract.

Tests passed for success then failure, startup failure, stopped updates and unexpected shape. We also tested recovery: a new successful reply restores the live value and updates its time. The failed or stale tile stays unavailable until then. Thanks, Lin; stopping updates found the bit our parser tests missed.

Good, and the next person looking at the training screen won't have to guess whether its cheerful answer is still alive.