Apps 365 update log analysis

The ThroVal are internal/private values used by Microsoft to determine if a device should already adopt a new build or check again during the next update discovery (which happens every 24hrs if I recall correctly).

Things were a bit different in July, as an issue with Access was discovered (https://support.microsoft.com/en-us/topic/error-when-trying-to-open-an-accde-mde-file-created-in-a-different-version-of-access-f4cd36cd-549e-42ba-b75a-dfe964294a81) and Microsoft released a new update with a fix for this issue.

So timeline for a given device could have been (longest-possible scenario):

Update released on 7/12.
Before the per-device throttle value allows the update to be downloaded & applied, Microsoft stopped the rollout (around 7/15) and started working on a fix.
Fixed release made available on 7/26, as usual, released in a staged manner.
Again, device is randomly throttled and gets the clearance to get the new update 4-5 days later.
On ~7/31, the device meets the throttle value and is allowed to install the new update.
Now the deferral you set kicks in. The device waits for another 24 hrs before downloading the update. (Deferral counts from the beginning of the individual device becoming aware of the pending update, not from the point in time when Microsoft releases a new update).
On 8/1 the device downloads the update, can't apply as apps are running and waits another 24 hrs before nagging the user (your setting of deadline=1 day).
The user can postpone the actual application of the update for ~48hrs.
So on 8/3 latest, the update should be installed.

As mentioned, above is the "slowest scenario". Other device might meet the throttle settings on day 1 (7/26), device downloads on 7/27, user has no apps open and the update is applied right away. Job done.