Skip to content

fix(google-calendar-sa): deduplicate events across impersonated emails#474

Merged
JonasJesus42 merged 2 commits into
mainfrom
fix/scheduler-dedup-no-email
Jun 24, 2026
Merged

fix(google-calendar-sa): deduplicate events across impersonated emails#474
JonasJesus42 merged 2 commits into
mainfrom
fix/scheduler-dedup-no-email

Conversation

@JonasJesus42

@JonasJesus42 JonasJesus42 commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Same meeting visible to multiple impersonated emails caused duplicate notifications. Dedup key now excludes email.


Summary by cubic

Prevents duplicate notifications in google-calendar-sa when the same meeting appears under multiple impersonated emails, and stops notifying for meetings that already started.

  • Bug Fixes
    • Deduplicate by ${connectionId}:${eventId}:${startTime} (removed email) to avoid cross-email duplicates.
    • Skip events with minutesUntilStart < 0; only notify when 0 <= minutesUntilStart <= leadMinutes.

Written for commit d0c06ca. Summary will update on new commits.

Review in cubic

JonasJesus42 and others added 2 commits June 24, 2026 17:14
Events with minutesUntilStart < 0 were not filtered, causing past
meetings to trigger notifications on first scheduler tick.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
The same meeting appears in multiple impersonated emails. Including the
email in the dedup key caused duplicate notifications across scheduler
ticks. Now the key is connectionId:eventId:startTime.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@JonasJesus42 JonasJesus42 merged commit 571b768 into main Jun 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant