I have been seeing a similar issue in Rancher 2.6. if you force an update in the GUI it will get the correct state. It seems like there is some kind of bug in fleet whereby sometimes the Rancher server is not correctly updated with fresh status from downstream cluster.
But this is only what I have observed from my hand cranked prototype that I spun up to evaluate the platform. 🙂
Nothing to say there isnt an issue with my setup 🤣