-
Notifications
You must be signed in to change notification settings - Fork 346
Crash on Status 429 (Too Many Requests) #164
Comments
Is there a way of self-throttling? |
I got same results. After syncing ~20GB the Skilion/OneDrive client interrupted with status code 429. One hour later I ran it again. OneDrive let me sync ~1GB and then the client interrupted again. OneDrive seems limited. So the client could react to this status code. Fortunately a cron can be solution. |
Hi, I have the same issue. I made a workaround by adding retry function: diff --git a/src/onedrive.d b/src/onedrive.d @@ -132,7 +132,15 @@ final class OneDriveApi
@@ -300,7 +308,7 @@ final class OneDriveApi
|
@tdaff can you replicate this with the latest release? |
@thomasfedb sorry, I'm not able to test it anymore, gone back to Windows! Maybe someone else can test it, but it's not an issue for me anymore. |
@tdaff might be best to close this issue in that case. Cheers. |
Can you close this case if no longer applicable ? |
@tdaff |
Considering this issue closed due to no response from original submitter. If you have further issues please or come back to this, open a new case here: https://github.com/abraunegg/onedrive |
I'm getting this issue myself. I believe it is related to the amount of HTTP requests sent to the server rather than the about GBs synced. It looks like the client app is sending a request per file, so if the are multiple small files, the server bounces with a Too Many Requests response. Looks like the amount of requests should be throttled, although I wonder if there is a way to bulk get files to avoid sending soo many requests to the server. |
I am getting the same issue, half way through retrieving all of my data from OD, 56 gb to go but it seems to constantly spit this now, even after waiting for 12 hours it only just downloaded 3 gb more before spitting it again. After that when resuming it manages to get some files 50 maybe sometimes less, sometimes not even 2 :), and raises again. At this point I kind of ran out of ideas. Tried to log out and log in again but seems not able to get passed this error. Will try on a different pc as soon i sync some other data and will be able to change the conf matching the failing setup on initial machine. |
Just started using this and I'm getting this issue as well. |
@wn2000 Regarding your specific issue, 429 responses are correctly handled in the above supported codebase. Major differences / Enhancements:
|
@abraunegg Thank you! Will give it a try. |
After syncing about 20 GB in many files over the course of an hour, I started getting limited. Apparently the status comes with a
Retry-After
header, but maybe it is worth slowing down requests for a while if you get a 429 in the middle of a complete re-sync?Unfortunately I don't think the limits are made publicly available.
The text was updated successfully, but these errors were encountered: