You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Make for a client to automate a process which performs the following actions, involving Onedrive Personal :
Detect and list changes on files on a Onedrive Personal account
Pick one .doc / .docx file recently updated/created on Onedrive, download it as PDF, compress it and then upload it to the same folder on Onedrive
Create one sharing link (type = "embed") with an API call : /v1.0/me/drive/items/{{id}}/createLink (this feature is not available on Onedrive Business : I tried to solve my problem ).
Create one sharing link (type = "view") with an API call : /v1.0/me/drive/items/{{id}}/createLink
Add these links to a Firebase database in order to display the PDF documents on my client's website
Here is the unfortunate issue I'm encountering for 2 years now (the same as the one described here : #1436)
I'm getting throttled after only 8-10 links created in 40 minutes. Moreover, there is absolutely nothing in the response header, like a retry-after value for example (screenshot below)
I've implemented a backoff waiting 120 minutes before retrying, but it's still getting throttled after 8-10 API calls (createLink).
The limit is incredibly low, and it looks that there is no way to increase it or the perform a proper backoff mechanism. There is only this problem with createLink API.
My questions are (by order of importance) :
1. What is the theoretical limit of createLink API calls for Onedrive Personal ? I haven't been able to find this information on any official documentation.
2. Is there a way to increase the limit of API calls (8 calls in 40 minutes before getting throttled : it's quite few...), or at least to receive the retry-after header in order to perform a proper backoff mechanism with Make ?
3. Why doesn't OneDrive for Business support the creation of "embed" sharing link, while this feature is supported by Onedrive Personal ?
4. If you can't answer any questions above : do you know a cloud storage that allows to create embed links and download links for PDF files with API calls ?
I'm really stuck after a large amount on time dedicated to this project, my workflow is fine but this 429 Too many requests error is ruining the project...
The text was updated successfully, but these errors were encountered:
Hello,
I'm using Make for a client to automate a process which performs the following actions, involving Onedrive Personal :
Here is the unfortunate issue I'm encountering for 2 years now (the same as the one described here : #1436)
I'm getting throttled after only 8-10 links created in 40 minutes. Moreover, there is absolutely nothing in the response header, like a
retry-after
value for example (screenshot below)I've implemented a backoff waiting 120 minutes before retrying, but it's still getting throttled after 8-10 API calls (
createLink
).The limit is incredibly low, and it looks that there is no way to increase it or the perform a proper backoff mechanism. There is only this problem with
createLink
API.My questions are (by order of importance) :
1. What is the theoretical limit of
createLink
API calls for Onedrive Personal ? I haven't been able to find this information on any official documentation.2. Is there a way to increase the limit of API calls (8 calls in 40 minutes before getting throttled : it's quite few...), or at least to receive the
retry-after
header in order to perform a proper backoff mechanism with Make ?3. Why doesn't OneDrive for Business support the creation of "embed" sharing link, while this feature is supported by Onedrive Personal ?
4. If you can't answer any questions above : do you know a cloud storage that allows to create embed links and download links for PDF files with API calls ?
I'm really stuck after a large amount on time dedicated to this project, my workflow is fine but this
429 Too many requests
error is ruining the project...The text was updated successfully, but these errors were encountered: