Google Calendar API异常：参会者已接受但自身日历无对应事件

Hey there, let's walk through the likely causes for this odd behavior you're seeing with the Google Calendar API. Since you can't replicate it with your own accounts and it only affects ~5% of meetings, it's probably tied to specific user settings, event configurations, or edge-case permissions:

1. Event Visibility & Calendar Settings for User B #

• If the meeting organizer set the event's visibility to confidential or private, and User B's calendar permissions don't allow viewing such events from the organizer's calendar, the event might not sync to B's primary calendar—even though B accepted the invitation.
• Check if User B has the "Automatically add invitations to my calendar" setting disabled (or set to a restrictive option like "Only show invitations I've responded to, but don't add them to my calendar"). If B manually accepted the invite but chose not to add it to their primary calendar, the event won't appear in primary calendar queries, even though their response status shows as accepted in the organizer's/a's event view.

2. Service Account Delegation Permissions Gaps #

• Even if your service account has domain-wide delegation, it's possible that for User B specifically, the domain admin didn't grant the necessary calendar scopes (e.g., https://www.googleapis.com/auth/calendar.readonly) correctly. Double-check the admin console to confirm the service account is authorized to access B's calendar.
• Also, ensure that when you're querying B's calendar, the service account is properly impersonating B (your code uses the correct credentials delegated to B's email—sometimes typos or incorrect delegation targets can cause silent permission failures).

3. Event Ownership & Shared Calendar Context #

• The meeting might have been created in a shared calendar (not the organizer's primary calendar). User A might have subscribed to this shared calendar, so the event appears in A's primary calendar view, but User B hasn't subscribed to it. Since you're querying calendarId='primary' for B, the event won't show up unless it's explicitly added to B's primary calendar.
• If the organizer later removed User B from the event, A's calendar might still retain a cached version of the event with B's old accepted status, while B's calendar no longer has any record of it. However, you mentioned showDeleted=True didn't help, so this is less likely unless the deletion was processed in a way that didn't mark the event as deleted in B's calendar.

4. Time Zone Mismatch in Query Parameters #

• Your timeMin and timeMax are formatted in UTC (+0000), but if User B's calendar uses a different time zone, the event's actual time in UTC might fall just outside your query window. For example, an event that starts at 07:30 UTC might be within your 08:00 start time when viewed in A's time zone, but in B's time zone it's a different date that's excluded from your query. Double-check that your time range fully covers the event's UTC start/end times.

5. Google Calendar Internal Sync Delays or Data Inconsistencies #

• Rarely, Google Calendar can have temporary sync issues between user calendars. If the event was recently updated or accepted, B's calendar might not have synced the change yet. Since this affects only 5% of meetings, it could be intermittent sync gaps that resolve on their own, but it's worth considering if the problematic events are all recent.

6. Edge Case with Recurring Events #

• If the event is part of a recurring series, a modified instance might not sync correctly to B's calendar. Even with singleEvents=True, if the instance was deleted or altered in B's calendar (but not in A's), you might see this discrepancy. Again, showDeleted=True should return deleted instances, so this is a stretch—but worth checking if the problematic events are recurring.

内容的提问来源于stack exchange，提问作者lmaayanl