How does local OneDrive determine if a local file needs to be updated?

When using multiple computers to edit a OneDrive file, a computer often fails to recognize its local copy needs to be updated, even though the file on all computers is set to "Always keep on this device."  This means changes are lost with no conflict error generated.  Is the OneDrive algorithm for deciding when to update a local version of a file documented anywhere?

Usually when a change is made to a file, it starts uploading to the cloud within seconds.  Within several seconds after the changed file is uploaded, other computers will recognize their local copy is outdated and will begin downloading the changed version.  That is the expected behavior.  But often, that doesn't happen.  The outdated version is used to make new changes.  Those new changes are uploaded successfully.  No conflict warning is generated.  The earlier changes are lost forever.

I have not found any documentation on how local Windows OneDrive decides if its local version of a file needs to be updated.  Is it looking at file size?  Timestamps?  If timestamps, is there a margin of time sync differences?  Does the OneDrive metadata include the source device of the last upload?  Not knowing any of this I cannot troubleshoot the problem much beyond establishing that the problem is not with uploading changes.  OneDrive local is reliably uploading changes.  MD5 hash codes in the cloud match the hash of the changed file on the source computer.

I don't have time to jump through hoops with someone at frontline Microsoft support who doesn't know any more about the algorithm than I know in order to get the issue escalated to someone with the information needed to pinpoint the issuse.