It might be helpful to see timing details, for example with log-file=<path> and log-file-log-level=verbose.
Throttle Not Working was a big thread on this, where somebody was trying to get a steady upload rate.
Although a code change was made at the end (more on that later), an early thought was to tune things.
Microsoft OneDrive v2 (Microsoft Graph API)
--fragment-size (Integer)Size of individual fragments which are uploaded separately for large files. It is recommended to be between5-10 MiB(though a smaller value may work better on a slower or less reliable connection), and to be a multiple of320 KiB. Default value:10 MiB
was mentioned by the developer, but there are also --fragment-retry-delay and --fragment-retry-count available. These are OneDrive-specific, and there are also file (not fragment) level generic options number-of-retries and retry-delay. Your message says Retry-After: 55. The code change I can see is mentioned here in the thread, and discussion continues at PR Try to fix OneDrive upload throttling #4469.
Fixed throttling requests to OneDrive and respecting the server
retry-afterheaders, thnaks @tygill
but the catch with this way is that the change is not yet in a Beta. If you want to run the latest Canary and decide more carefully (for example by watching form (especially Releases category for added breakages, perhaps that may work. In a later Canary, there’s another change to do retries the way some servers like:
Added exponential backup for retries, thanks @vmsh0
If you decide to try the OneDrive-specific options, adding them on the Options screen is safer, as additions done on the Destination screen sometimes get lost. While on Options, make sure that the Remote volume size is something not hugely different from default 50 MB. Very large values might complicate this situation.
I suppose there’s also a chance that waiting a day will see a better situation if something resets or clears…