Closed prossberg closed 2 years ago
It is an issue with one of the API's used to interact with Notion's API being rate limited. I released an update that, along with some bug fixes, should hopefully reduce the chance of this happening.
Got it. The best way to update is just copy the new contents of the file over the old and redo changes to variable names right?
Yup. Make sure to double check if anything changed in the structure of the database but for this update there shouldn't be any changes.
Worked without errors. This integration is awesome and so is your support.
Hey! I implemented this integration a few days ago (with the latest code updated), but I still get the mentioned error.
5:44:38 PM Error
Exception: Service invoked too many times for one day: urlfetch.
notionFetch @ Code.gs:480
syncToGCal @ Code.gs:75
main @ Code.gs:31
Any recommendations for me?
Hey! I implemented this integration a few days ago (with the latest code updated), but I still get the mentioned error. 5:44:38 PM Error
Exception: Service invoked too many times for one day: urlfetch. notionFetch @ Code.gs:480 syncToGCal @ Code.gs:75 main @ Code.gs:31Any recommendations for me?
You're being rate limited. Reduce the frequency for which you are auto triggering the script. It might also resolve itself in a day anyways because the initial setup and sync will require a lot of API calls. However, since you said that you are getting the error even after a few days, you are likely just calling the script too often.
I have one of the triggers set up to be every 15 minutes. This worked fine up until yesterday when I swapped the code I used for a newer version. The it started failing and throwing errors. First this longer error:
The after a few failed attempts it just went down to this:
immediately after starting the sync to GCal.
Is this a problem with Notion receiving to many requests or something else?