That sounds to me like there’s an issue with the way the performance collection rule has been created.
Is the collection using some kind of dynamic value? If so, it’s likely being stored as a different object/metric each time the discovery runs and you’ll see this in a SCOM report too.