IssueTracker

I have identified the problematic property:

  "outOfOfficeProperties": {
    "autoDeclineMode": "declineAllConflictingInvitations",
    "declineMessage": "Out sick, but available for important or urgent matter "
  }

Import works again after removing it.

Confirming the removal of outOfOfficeProperties (via delete event.outOfOfficeProperties) does fix the problem. Thanks!

I have forwarded this to the engineering team. Another request failing with 400 but not having the outOfOfficeProperties field would be helpful. Thank you.

Our script also broke for syncing individual time off to a shared team calendar. In my case I had to delete the outOfOfficeProperties attribute and also change the eventType to default as the outOfOffice eventType is not supported in shared calendars.

function importEvent(username, event) {
  event.summary = '[' + username + '] ' + event.summary;
  event.organizer = {
    id: TEAM_CALENDAR_ID,
  };
  event.attendees = [];

  // remove outOfOfficeProperties to support importing outOfOffice events
  // see https://issuetracker.google.com/issues/313935022?pli=1
  delete(event.outOfOfficeProperties);

  // switch event type to default, cannot create `outOfOffice` events in shared calendars
  event.eventType = 'default';

  console.log('Importing: %s', event.summary);

  try {
    Calendar.Events.import(event, TEAM_CALENDAR_ID);
  } catch (e) {
    console.error('Error attempting to import event: %s. Skipping.',
        e.toString());
  }
}

I can confirm, I also had to set

event.eventType = 'default';

to make it work again.

True, looks like the new error started at midday December 15th.

Why on Earth is there try/catch instead of sending error alerts (when run via triggers) like a normal script...?

My solution is therefore a new variable called TEMPORARY_FIX and checking for it inside the relevant function (but note I only do this for eventType outOfOffice):

let TEMPORARY_FIX = true;
...
function importEvent(username, event) {
...
  try {commonmark.org
    if (typeof TEMPORARY_FIX !== 'undefined' && TEMPORARY_FIX && event.eventType == 'outOfOffice') {
          delete event.outOfOfficeProperties;
          event.eventType = 'default';
    }
    Calendar.Events.import(event, TEAM_CALENDAR_ID);
  } catch (e) {

Can confirm that the following worked for me prior to importing events on the shared calendar:

delete event.outOfOfficeProperties;
 event.eventType = 'default';

The sample script at https://developers.google.com/apps-script/samples/automations/vacation-calendar has been updated to work again! I am going to leave this open until I have confirmed the underlying API is functioning as expected. Thank you for your patience.

Thanks!!! And as an added bonus, since this got you to finally copy/paste the GitHub version into the official developer site, it means the official version finally contains my 2 features (support for indirect members and support for multiple groups)!

Maybe you should consider always syncing the official version to GitHub? In this case it could have solved this bug almost 2 months ago.

To answer your question, I can just quote myself from above:

Why on Earth is there try/catch instead of sending error alerts (when run via triggers) like a normal script...?

That's why you'll never get any errors. This goes against the whole principle of Triggers. I suggest remove the try/catch and then you'll finally get errors and maybe know what was wrong.

P.S. Did you also add the service as explained in "Create the Apps Script project"?

I am marking this issue as FIXED as the internally reported issue has been marked as FIXED. Please note that there may be a delay in rolling this out to production. Thank you for your patience and please comment here if the issue remains.

This was prematurely closed via an automation as one of the blocking issues was resolved. I set this as blocked by some other work that is underway at the API level to fix this.

I am marking this issue as FIXED as the internally reported issue has been marked as FIXED. Please note that there may be a delay in rolling this out to production. Thank you for your patience and please comment here if the issue remains.