Summary

Sam approved the notification-safe SAIL Boat calendar pilot. The target calendar was resolved and read successfully, but shared-calendar writes failed with Outlook 403 ErrorAccessDenied.

What Was Verified

• Calendar resolved: SAIL Boat.
• Owner shown by connector: Nathaniel Hatfield / Hatfield@kylawoffice.com.
• Connector metadata showed can_edit=true, but write calls still failed.
• Existing January 26, 2026 WFH events are no-attendee appointment blocks with reminders off, which confirms the proposed notification-safe shape is already how this calendar appears to be structured.

Pilot Attempted

The pilot targeted three existing no-attendee WFH events only, to avoid duplicates:

• Adam WFH -> proposed Adam M. - WFH, Salesforce record a4RUV0000044svZ2AQ.
• Katie WFH -> proposed Katie H. - WFH, Salesforce record a4RUV0000044scD2AQ.
• Donna WFH -> proposed Donna G. - WFH, Salesforce record a4RUV0000044sfR2AQ.

Result

All three shared-calendar update calls returned:

403 ErrorAccessDenied: Access is denied. Check credentials and try again.

No SAIL Boat calendar events were created or updated.

Local Artifact

/Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/pto-2026-title-and-candidate-cleanup-2026-05-12/sailboat-calendar-pilot-write-blocked-2026-05-12.md

Suggested Next Step

Refresh/reconnect the Outlook Calendar connector or use another authenticated Microsoft Graph lane with delegated shared-calendar write permission, then rerun the exact same three-record no-attendee pilot. Once that succeeds, expand to a small batch and then the remaining 2026 reconciliation set.