Servicing Plans should evaluate builds on Availability Date not Revision Date
Servicing Plans, effectively, don't work anymore. I had this process setup to be automated with different deployment phases at 30, 90 and 180 days. This process no longer works because Microsoft has been releasing newer versions of the upgrades that reset the release date.
So now build 2004, which released over 300 days ago, doesn't qualify for my 180 day General Release plan. Microsoft released an updated upgrade file on 11/9/2020, only 142 days ago. This revision was also 14 days BEFORE the 180 days was up, so build 2004 was never picked up by my Servicing Plan.
This forces me to either manually manage Servicing Upgrades, or I have to rework my testing phases and then still have to keep monitoring for new revisions that could mess it all up.
Servicing Plans need to be based on the Availability Date of the the Build ( https://docs.microsoft.com/en-us/windows/release-health/release-information ) and NOT the Revision Date.