Skip to content
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

Gmail error handling fixes #8732

Merged
merged 1 commit into from
Nov 26, 2024
Merged

Gmail error handling fixes #8732

merged 1 commit into from
Nov 26, 2024

Conversation

bosiraphael
Copy link
Contributor

Gmail error handling fixes

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This PR enhances Gmail message import error handling by improving error code detection, message extraction, and sync stage accuracy across multiple services.

  • Modified error code detection in /packages/twenty-server/src/modules/messaging/message-import-manager/drivers/gmail/services/gmail-handle-error.service.ts to use error.code instead of error.response.status
  • Added proper error message extraction from both direct error objects and response data in Gmail error handling
  • Replaced calendar-specific constant with MESSAGING_THROTTLE_MAX_ATTEMPTS for message import throttling
  • Fixed refresh token exception handling syntax in /packages/twenty-server/src/modules/messaging/message-import-manager/services/messaging-messages-import.service.ts
  • Updated sync step from PARTIAL_MESSAGE_LIST_FETCH to MESSAGES_IMPORT for accurate error stage tracking

3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

@charlesBochet charlesBochet merged commit 08f1635 into main Nov 26, 2024
19 checks passed
@charlesBochet charlesBochet deleted the r-fix-error-handling-gmail branch November 26, 2024 10:22
Weiko pushed a commit that referenced this pull request Nov 26, 2024
Gmail error handling fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants