Elevated 504 Errors When Sending Messages via Google
Incident
Report for Nylas v3
Resolved
We are now resolving this incident, as error rates have returned to pre-incident levels and have remained stable—even during peak usage periods. While we have not received formal confirmation or a root cause analysis (RCA) from Google Workspace Support, we continue to follow up with their team and will share any relevant findings if and when they become available.
Thank you for your patience throughout this issue.
Thank you for your patience throughout this issue.
Monitoring
While we have not yet received an update from Google, we are now observing that the rate of 502 errors from the Gmail API (which surface as 504 errors via Nylas) has returned to normal levels as of this morning—even during peak usage periods. Given the sustained improvement, we are moving this incident into a Monitoring state.
We are continuing to push Google for confirmation of a fix on their side, as well as a root cause analysis (RCA). We will post additional updates here as they become available.
If you are still experiencing elevated error rates, please contact us at support@nylas.com.
We are continuing to push Google for confirmation of a fix on their side, as well as a root cause analysis (RCA). We will post additional updates here as they become available.
If you are still experiencing elevated error rates, please contact us at support@nylas.com.
Update
We continue to work directly with Google Workspace Support—the team responsible for the Gmail API—and are providing additional logs and data to support their ongoing investigation. While Google has not yet provided an ETA for resolution, we are actively escalating the issue on our end. In parallel, the Nylas engineering team is exploring potential workarounds to reduce the impact of these intermittent errors. We will continue to share updates here as they become available.
Thank you for your continued patience—we understand the impact this may have on your workflows and are treating this with the highest urgency.
Thank you for your continued patience—we understand the impact this may have on your workflows and are treating this with the highest urgency.
Update
We have submitted a high priority bug ticket to Google for further investigation into the intermittent 502 errors (returned by Gmail, surfaced as 504s by Nylas). Along with the ticket, we included detailed logs and a sample payload to support their analysis.
We’re continuing to monitor the situation closely and will provide updates as soon as we receive a response from Google.
Thank you for your continued patience.
We’re continuing to monitor the situation closely and will provide updates as soon as we receive a response from Google.
Thank you for your continued patience.
Update
We’ve observed a noticeable decrease in the number of 502 errors from Google when sending messages (Nylas 504s). However, some errors are still occurring.
Our team continues to monitor the situation closely, and we’ll share another update as soon as we have more information.
Thank you for your continued patience.
Our team continues to monitor the situation closely, and we’ll share another update as soon as we have more information.
Thank you for your continued patience.
Investigating
We are currently investigating an increase in 504 errors when sending messages through Google accounts via the v3/message/send endpoint. This appears to be related to a temporary error on Google’s side, as we are receiving the following response from their servers:
502. That's an error.
"The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds. That's all we know."
Our engineering team is monitoring the situation closely and has opened a support ticket with Google to gain further insights. We will provide updates as more information becomes available.
Thank you for your patience and understanding.
502. That's an error.
"The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds. That's all we know."
Our engineering team is monitoring the situation closely and has opened a support ticket with Google to gain further insights. We will provide updates as more information becomes available.
Thank you for your patience and understanding.
This incident affected: Nylas Application Services (API v3) and 3rd Party Providers (Google).