Our dashboard for diagnostic status retrieval on Fairino FR5 expected a status value from the old SDK. The replacement environment returns a container with extra information, and our screen now shows a plausible status even when a request fails.
This is in a training cell with a read-only dashboard, with a reference bracket as a reference. I'm trying to fix how we interpret the answer.
@JoAli0244 I've checked our saved examples. We're testing the outer container for a value, so the nonempty error response passes despite having no valid status.
@JoAli0244 Two examples establish the reported bug, but they don't cover an adapter. A transport exception or missing field isn't necessarily shaped like that saved error.
@SofiaBaker0456 Fair point; I overstated coverage. Keep those as the regression, then add documented errors, transport exceptions and malformed replies
I've got an answer to the design question: parse the documented status for the identified SDK and keep failures unavailable. I'll call the display fix complete only when our offline examples show that behaviour on screen.