Balena Cloud Release Change Not Finalised


We have a device that was moved from one fleet to another. This appears to work, but the dashboard does not reach a correct and final state.
In the interface, despite all containers reporting that they are running software from the latest release, the current release SHA of the device does not appear to change and the containers appear in a transitioning state.

Why does this occur?


Thanks for the help!

Hello @louisburton ,

Sorry for the late response, are you still facing this issue? We’ve had some hiccups in the platform during that time, but that should be resolved now.


I believe this was resolved by a supervisor upgrade. I had read this symptom elsewhere after this post linked to a bug in the supervisor.
Thanks for checking in.

Thanks for the confirmation! Glad to hear it’s been resolved.