Zapier Status · History · Incident #5793
RESOLVEDQuota exceeded errors on a subset of Zap runs using Google apps integrations
Minor · Started Jul 22, 2026 · 6:32 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Zapier Status · History · Incident #5793
RESOLVEDMinor · Started Jul 22, 2026 · 6:32 PM
Duration
2h 6m
Severity
Minor
Detection lead
—
User reports
—
Summary
We previously reported quota-exceeded errors affecting a subset of Zap workflows using Google Drive, Google Sheets, Google Docs, Google Slides, and Gmail actions. The underlying issue has been fixed. Affected Zap runs have been replayed, and workflows that were paused due to elevated errors have been restored. No further action is needed on your end. If a Zap run still shows as failed, you can replay it from your Zap history, or contact Support at [zapier.com/get-help](http://zapier.com/get-help "zapier.com/get-help").
Started
Jul 22, 2026 · 6:32 PM
Resolved
Jul 22, 2026 · 8:38 PM
Duration
2h 6m
Severity
None
Event timeline
Monitoring
Jul 22 · 6:32 PM ZapierWe have confirmed that the Quota Exceeded errors from Google Drive also affected a small subset of Zap workflows using Google Sheets, Google Docs, Google Slides and Gmail actions. The Google Drive quota exceeded errors have been resolved (<https://status.zapier.com/incidents/01KY534ZVKCPV90WN0B6BAY0WY>). The majority of affected Google apps Zap runs have been replayed. We are currently monitoring error rates and confirming that all affected Zap runs have succeeded at this point. If you have any questions, please reach out to our Support team at zapier.com/get-help.
Resolved
Jul 22 · 8:38 PM ZapierWe previously reported quota-exceeded errors affecting a subset of Zap workflows using Google Drive, Google Sheets, Google Docs, Google Slides, and Gmail actions. The underlying issue has been fixed. Affected Zap runs have been replayed, and workflows that were paused due to elevated errors have been restored. No further action is needed on your end. If a Zap run still shows as failed, you can replay it from your Zap history, or contact Support at [zapier.com/get-help](http://zapier.com/get-help "zapier.com/get-help").
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.