Exactly!
And just to elaborate on this a bit, based on the data collected in the tracker, and on what people have been reporting, there is no evidence to suggest that when an update is recognized as having a bug, and thus OTA pushes are stopped, that service centers are notified as well, and stop installing those specific updates. Tesla internal communications just aren't that good, or this just isn't deemed important enough.
Now don't get me wrong: I expect if there was a really significant issue or one that posed a safety concern, Tesla would communicate properly, and prevent the update in question from being installed on additional cars. But to date that has not been the issue, as the bugs have, for the most part, been relatively minor. It appears the typical progression is the bug is identified, OTA updates stop, a new version is released via OTA, and usually the following day that new version begins being installed at the service centers. Until the new version hits the service centers, the old, buggy version would still be installed at service centers during that usually short interim period between when the buggy version was no longer pushed OTA and the fixed version was released.
