Closed astronaut954 closed 1 year ago
For the execution time out stuff, see the wiki for some suggestions to get around it. https://github.com/hk21702/YA-GCal-Notion-Sync-Script/wiki/FAQ-&-Common-Errors#i-got-an-execution-timeout-error
The recurring events being a bit excessive on larger time scales is unfortunately a GCal API thing that isn't easily fixed without setting a limit for all your events.
The deleting cancelled tag error is because it needs both the calendar ID and the event ID. If you're missing even just one, it will spit out that error in the console. It was likely due to a bug that I just recently fixed in #32. Update your script to the latest version and that error should be resolved.
The duplicate entries error is unfortunately a bit hard to solve. It is a known issue that sometimes crops up due to synch and timing issues with talking with the APIs.
The big error you got is Notion's issue. It appears that they were down at that time.
Hi @hk21702, thank you for the response! I used the wiki suggestion (sorry, didn't see it before) and now I have a more reliable database. Limited to 3650 days, so I will have 10 events for each date. Yet, from what I understood, if it reaches the last event of the 10 events, it won't create new ones, right?
Also, kinda off-topic, I think in the near future Notion will add recurring tasks (not only for templates), I think it will make everything more smooth if you update the script with this new feature, since it won't need to create hundreds and hundreds of new events.
Glad to hear that things are working out better. You are correct in your understanding. The date limit is not one that shifts in real time. If you want to get events past the limit that you've set, you'd need to do a full sync due to GCal API limitations.
I know you crossed the last bit out, but just as a comment, it would really depend on how Notion implements it. Since in GCal you have the ability to modify individual events in a series of recurring events, depending on how Notion implements recurring tasks in databases, it could get really messy to try and translate between the Notion implementation and GCal.
This issue has not had any activity for an extended period of time and is thus automatically being marked as stale.
@${author}, you can help out by closing this issue if the problem no longer exists, or adding more information.
This issue has been closed automatically because it needs more information and has not had recent activity.
I'm trying to sync my Calendar with recurring dates. All the events in this calendar are recurring. There is a total of
45 events55 events that will recur annually, considering that each event will have a total of 30 copies(so far is what the script sent)there will be a total of 1650 pages. The problem is that there is this "Rate limit" that Notion has that you can find here :Since I have to first do a
FULL_SYNC
to get all the events it will have A LOT of requests, so at some point, I will get this error:I waited for the minutes it asks and ran the script again. Yet I found an issue, it will look for updates in every single event, even if the
IGNORE_RECENTLY_PUSHED
is turned on. I looked for the total of pages in the database and I have 1322, so I guess it is missingonly 28 of all the pages I need.Any idea on how to solve this? I thought about setting a delay after the
Rate limit
has been reached, so it will wait a few minutes and after this time it will continue the script from where it stopped, yet this would also need to cancel the next time trigger, so it won't conflict.UPDATE:
I've managed to solve the problem by deleting some events, cleaning all the database, and starting a fresh
FULL_SYNC
. Yet I'm facing another problem now. If I update too many events at once, I will get aTIMEOUT
(30 minutes) of the Apps Script. Even if the NotionRate Limit
hasn't been reached, I get thisTIMEOUT
because the script has too many new entries to look at, it does get really big very easily. The script doesn't seem to continue from where it stopped, so it gets "stuck" because it will loop infinitely.Also, I've noticed some strange behaviors now, here is the list:
FULL_SYNC
without reaching theRate limit
, so after doing it I added again all the events by creating new ones with the exact same settings). And when deleting those duplicated events the Apps Script console would say it couldn't find theEvent ID
even though there was an ID in the page.