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.