Autopatch Bug with Autopilot Devices

We have noticed a bug with Autopilot Devices and Autopatch.  If an OEM uploads Devices into Autopilot and we have a Dynamic Group based on the Autopilot Tag that they get added to that is also used for the Autopatch Device Registration, The Autopatch service will attempt to register before the device is even taken out of the box and will never register with the service after being deployed.  Example OEM Uploaded Devices to Autopilot on 7-15-22 with Group tag that adds the device to a Dynamic Group which also creates the Azure AD Device Record with the Serial number of the Device, Device was Deployed on 9-5-22 which then creates the Intune record, Autopatch shows the devices tried to register on 7-15-22 but failed due to device not yet being Intune or Cloud-Attached as device had not been deployed yet. Device is now currently deployed but still shows not registered in Autopatch due to Intune or Cloud-Attached even though the device is now deployed. Device shows in autopatch with the serial number as the Name (eg when the autopilot service created the record) and not with the current PC name as autopilot renames the PC on deployment.