I noticed our diagnostic screen reporting the same reassuring status after an SDK request failed. The new library returns a container where the old wrapper expected a value. Has anyone dealt with the display side of this, especially what the operator sees while no fresh answer is available?
What does the screen do with the previous value? I'd want it visibly stale, with its age, so nobody reads a perfectly green box as a fresh answer while they're trying to sort a stoppage.
It keeps the value and loses the failure information. We have checked the installed SDK's return format and are fixing the wrapper. The old screen gives no age indication either.
That's quite a cheerful screen you've got. Can you feed the revised display saved success and failure responses to see what an operator will actually get?
Try an empty or oddly shaped reply as well, because ours managed to turn a missing value into zero and zero happened to mean everything was fine. Nobody enjoyed that discovery.
Did you show the new version to someone on shift? Curious whether 'unavailable' and 'last known value' are clear when they're standing at the bench, rather than us staring at the code
Yes. They preferred the current status to say unavailable, with the last good value and age underneath. Failed and malformed responses now show that state in our checks. We have kept the detailed error available for maintenance.