I've been observing some events created on Gcal will get status cancelled after sometime.

{
"kind": "calendar#event",
"etag": "\"<some numbers>\"",
"id": "<id>",
"status": "cancelled",
"htmlLink": "=<eid>",
"updated": "2025-03-25T14:24:39.191Z",
"start": {
"dateTime": "1999-12-31T19:00:00-05:00",
"timeZone": "UTC"
},
"end": {
"dateTime": "2000-01-01T19:00:00-05:00",
"timeZone": "UTC"
},
"transparency": "transparent",
"iCalUID": "<id>@google"
}

1. The original start and end times get wrongly set
2. The event losses a bunch of fields which were originally set (summary, description, attendees, etc)
3. Making updates via api returns 403 (forbbiden) instead of 404 (for an event that is claimed to have been deleted.

{'domain': 'global', 'reason': 'forbidden', 'message': 'Forbidden'}

​I want to understand what could possibly happen for an event to be in this state.

​

I've been observing some events created on Gcal will get status cancelled after sometime.

{
"kind": "calendar#event",
"etag": "\"<some numbers>\"",
"id": "<id>",
"status": "cancelled",
"htmlLink": "https://www.google/calendar/event?eid=<eid>",
"updated": "2025-03-25T14:24:39.191Z",
"start": {
"dateTime": "1999-12-31T19:00:00-05:00",
"timeZone": "UTC"
},
"end": {
"dateTime": "2000-01-01T19:00:00-05:00",
"timeZone": "UTC"
},
"transparency": "transparent",
"iCalUID": "<id>@google"
}

1. The original start and end times get wrongly set
2. The event losses a bunch of fields which were originally set (summary, description, attendees, etc)
3. Making updates via api returns 403 (forbbiden) instead of 404 (for an event that is claimed to have been deleted.

{'domain': 'global', 'reason': 'forbidden', 'message': 'Forbidden'}

​I want to understand what could possibly happen for an event to be in this state.

​

• google-calendar-api

• Usually 403 messages is about authentication or user limitation from the entity that makes these requests. You might want to add more information about your current scenario that revolves around this so the community can help you better. Like adding your current code that pertains to this issue or current configuration and set up. – Babanana Commented Mar 27 at 13:03

1 Answer 1

This seems to happen when a user goes in to "Change Owner" after creating the event and you try retrieving the event via the old owner's calendar. Example, if the event was originally created on calendar_abc and is later goes through change of ownership to calendar_xyz, any operation on the event via the old calendar https://www.googleapis/calendar/v3/calendars/[email protected]/events/{event_id}/ will throw a 403 instead of 404.

This explains why the event info under the old calendar returns somewhat scrubbed info.