I’m wondering if this could be related to the number of events returned by the GET request (too many events in one response). The Google Calendar API usually returns a limited set of results and provides a nextPageToken for pagination. If the sync logic doesn’t handle pagination properly, it might stop after the first batch of events.
I would also like to know where I can adjust the sync time window (in which file or in the database) so that fewer events are requested from Google Calendar during each sync run.
Has anyone experienced this issue, or do you know if the plugin correctly handles large calendars with many events?
Hi Alex,
Thank you for the information.
I modified the default sync settings per provider directly in the database (from past = 30 / future = 90 → to past = 1 / future = 30 days). This workaround makes the sync work, but it’s not really suitable for my client, since the doctors need to manage bookings up to 90 days in advance.
Is there a way to go beyond the 250 events per request limit?
Would you be able to provide paid assistance on this? It’s a bit urgent, as my client went live on September 1st.
Best regards,