We've resolved an issue causing connection/authentication failures across Google Sheets, Google Drive, and Google Docs integrations.
A recent deployment introduced a change to Google authentication fields, which led to widespread refresh/stale authentication errors. This also had an impact on Agents and MCP workflows that use these Google integrations.
All impacts have been mitigated, and authentication error rates have returned to baseline.
If you're still seeing issues, re-check your workflows and reconnect your Google account if prompted. We also recommend reviewing your Zap history for any gaps during the incident window, especially for high-volume or business-critical workflows. If you identify missing data, you can re-process it by replaying the affected tasks in your Zap history or using Transfer to backfill: Transfer existing data using a Zap.
For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help.
No components marked as affected
Resolved
We've resolved an issue causing connection/authentication failures across Google Sheets, Google Drive, and Google Docs integrations.
A recent deployment introduced a change to Google authentication fields, which led to widespread refresh/stale authentication errors. This also had an impact on Agents and MCP workflows that use these Google integrations.
All impacts have been mitigated, and authentication error rates have returned to baseline.
If you're still seeing issues, re-check your workflows and reconnect your Google account if prompted. We also recommend reviewing your Zap history for any gaps during the incident window, especially for high-volume or business-critical workflows. If you identify missing data, you can re-process it by replaying the affected tasks in your Zap history or using Transfer to backfill: Transfer existing data using a Zap.
For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help.
Resolved
We’ve resolved an issue causing connection/authentication failures across Google Sheets, Google Drive, and Google Docs integrations.
A recent deployment introduced a change to Google authentication fields, which led to widespread refresh/stale authentication errors.
During the incident window, some workflows using these Google integrations may have failed to run, and some triggers may have missed events (especially high-volume workflows). There was no data loss.
We rolled back the affected Google integrations to their last stable versions and replayed held tasks for impacted users. Authentication error rates have returned to baseline.
If you're still seeing issues, re-check your workflows and reconnect your Google account if prompted. We also recommend reviewing your Zap history for any gaps during the incident window, especially for high-volume or business-critical workflows. If you identify missing data, you can re-process it by replaying the affected tasks in your Zap history or using Transfer to backfill: Transfer existing data using a Zap.
For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help.
Monitoring
We previously saw connection failures for Google Sheets, Google Docs, and Google Drive integrations, which caused some Zaps using these apps to stop running as expected.
We have applied a fix, and authentication error rates are now significantly decreasing.
There was no data loss, but some Zaps may have missed runs during the impact windows, particularly in high-volume workflows. Zaps using these Google apps should now be running normally again and picking up new data. We are also currently replaying any Zap runs that were held during the incident.
We’re monitoring the fix closely, and if you notice any ongoing issues, please contact Support: https://zapier.com/app/get-help
Identified
We have identified the cause of an ongoing issue affecting Google integrations, including Google Sheets, with some impact to Google Drive and Google Docs.
Users may experience intermittent connection or authentication errors, which can result in failed Zap runs or workflows not triggering as expected. In some cases, Zap runs may be delayed or temporarily held.
Our team is actively working on mitigation to restore stability. We are seeing early signs of improvement, but some users may continue to experience intermittent issues while mitigation efforts are ongoing.
We appreciate your patience as we continue to resolve this issue. We’ll provide further updates as progress continues.
