Skip to content

🐛 Fix: Handle NoSyncToken error during gcal notification #380

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 27, 2025

Conversation

tyler-dane
Copy link
Contributor

Logs instead message instead of full error to signify that this is a known scenario and not something we need to do anything about

Closes #379

logs instead message instead of full error to signify that this is a known scenario and not something we need to do anything about
@tyler-dane tyler-dane marked this pull request as ready for review April 27, 2025 23:00
@tyler-dane tyler-dane merged commit 9aab98c into main Apr 27, 2025
4 checks passed
@tyler-dane tyler-dane deleted the chore/379-sync-log branch April 27, 2025 23:01
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.

Notification not handled because no sync token found for calendarId: <calendarId>
1 participant