The 503 and 429 errors appear to be resolved at this point. Intermittent 502 errors are still present, but at much lower levels than before.

We are in communication with Google to see if we can understand why these errors continue to remain elevated.

We will be deploying a fix today to implement an exponential backoff on calls to this API to reduce the errors and properly retry them when we see 429, 503, and 502 errors from Google.

We are receiving HTTP error codes 403, 502, and 503 with information indicating that calls are being rate limited on the Google side. Because these error codes are not standard error codes for rate limiting (HTTP 429), our system may stop the Zap instead of correctly retrying it later.

You may see the following error messages in a Zap run at the Upload File Action: "We're sorry... but your computer or network may be sending automated queries." or "502 (server error)".