Downloading pinned release on every reboot

Anyone have an idea why a device would routinely download a pinned release on reboot when it successfully deployed before?

How does Balena set a flag to establish that the release was successful and an update isn’t needed?

Hi @drewcovi when did you start noticing this behavior?

Are you still experiencing this issue? If so, could you tell us about how you know the release successfully finished downloading? I know it may seem like a trivial question but I would like to begin debugging by confirming that the release indeed successfully downloaded. Screenshots would be helpful as well to ensure that I am seeing and understanding the same thing you are trying to communicate.