Skip to content

feat(gcal): implement exponential backoff and rate limiting for Google Calendar API requests#1654

Closed
tyler-dane wants to merge 1 commit intomainfrom
feat/gquota-backoff
Closed

feat(gcal): implement exponential backoff and rate limiting for Google Calendar API requests#1654
tyler-dane wants to merge 1 commit intomainfrom
feat/gquota-backoff

Conversation

@tyler-dane
Copy link
Copy Markdown
Contributor

@tyler-dane tyler-dane commented Apr 14, 2026

  • Added exponential backoff mechanism for handling rate limits in getEvents method.
  • Introduced sleep function to manage delays between retries and page requests.
  • Updated getBaseRecurringEventInstances and sync service to include rate limiting delays between calendar imports and event batches.
  • Enhanced error handling for Google Calendar API responses to improve reliability.

Related to #727

…e Calendar API requests

- Added exponential backoff mechanism for handling rate limits in getEvents method.
- Introduced sleep function to manage delays between retries and page requests.
- Updated getBaseRecurringEventInstances and sync service to include rate limiting delays between calendar imports and event batches.
- Enhanced error handling for Google Calendar API responses to improve reliability.
@tyler-dane
Copy link
Copy Markdown
Contributor Author

Closing to clean up the PRs. This is still good to reference once we get to #727

@tyler-dane tyler-dane closed this May 6, 2026
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.

Add quota user to Google Calendar API requests

1 participant