Thanks for the log snippet!
Taking this example you can see that odrive requested a rename, which was successful. “Local to Remote” means the change was seen on the local side and pushed to the remote.
22 Mar 09:55:38AM INFO Successful Move (Local to Remote) for /Users/oscar/odrive/Google Drive/MergeBase/legal/employment/signed/khahn-employment-letter-continue.pdf to /Users/oscar/odrive/Google Drive/MergeBase/legal/employment/signed/2022-03-22-khahn-employment-letter-continue.pdf
10 seconds later odrive requests a listing of the folder and sees that the file has been “renamed” on the remote side (in reality I think this is just that Google has stale information). “Remote to Local” means that odrive sees the change on the remote side and then mimics that on the local side.
22 Mar 09:55:48AM INFO Successful Move (Remote to Local) for /Users/oscar/odrive/Google Drive/MergeBase/legal/employment/signed/2022-03-22-khahn-employment-letter-continue.pdf to /Users/oscar/odrive/Google Drive/MergeBase/legal/employment/signed/khahn-employment-letter-continue.pdf
It isn’t included in the snippet you posted, and I haven’t seen a diagnostic come through yet to verify, but my guess is there is a later “Remote to Local” event that changes the name again, back to the name that was originally sent to Google in the “Local to Remote” sync event.