• Pertinent, most recent log file attached.

  • The log records the event's title, recurrence, and Google event ID, but the excerpt doesn't establish which Google calendar ID was queried. So we still can't say conclusively whether GCSM is reading the special Birthdays calendar directly or encountering a birthday-type event through another route.

  • the 11:47 run as the controlled test
    1. GCSM explicitly classified Joann's event as new
    At 11:47:05, the log says:
    No match found for Google appointment (Joann Michelle Price's birthday - 2022-10-20 Recurrence) => Add to Outlook
    That's direct evidence that GCSM decided to add the Google birthday appointment to Outlook.
    
    2. The Google event contains GCSM's private sync identifier
    At 10:29:48, the event's ExtendedProperties include a private property named gos:oid:Default_LWJPYX004. Google rejects GCSM's attempt to save that property because the event is of type birthday.
    This is an important clue: GCSM is trying to attach its synchronization metadata to an event that Google restricts.
    
    3. The log also shows that this isn't limited to Joann
    Gerald Keith Yelverton's birthday triggers the same API error. The log also shows other birthday and anniversary appointments being synchronized.
    
 

Last edit: John P Yelverton 2 days ago