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
In case of Google you can still fetch deleted events from the API even though they disappear in your calendar. In case of Microsoft they disappear both from the API and calendar, so they cannot be fetched in sync pods and synced there, the only way we can now something got deleted is in the webhook notifications.
To do less work (especially when cancelling recurrences with overrides) that could be potentially done in the background instead of marking events as cancelled directly in the api, store the uids of deleted events in a table event_cancellations(id PARIMARY KEY, calendar_id INT, uid TEXT, created_at DATETIME) and then change sync_events to fetch those events from database there, clone them, set as cancelled and then delete records from event_cancellations
The text was updated successfully, but these errors were encountered:
In case of Google you can still fetch deleted events from the API even though they disappear in your calendar. In case of Microsoft they disappear both from the API and calendar, so they cannot be fetched in sync pods and synced there, the only way we can now something got deleted is in the webhook notifications.
To do less work (especially when cancelling recurrences with overrides) that could be potentially done in the background instead of marking events as cancelled directly in the api, store the uids of deleted events in a table
event_cancellations(id PARIMARY KEY, calendar_id INT, uid TEXT, created_at DATETIME)
and then change sync_events to fetch those events from database there, clone them, set as cancelled and then delete records fromevent_cancellations
The text was updated successfully, but these errors were encountered: