How to troubleshoot errors in Zaps

Zaps can connect with over 6,000 apps, making it difficult to cover every specific error scenario. However, the following information can help you identify common errors you may encounter and discover solutions.

This guide will cover:

  • How to identify an error.
  • HTTP status codes, including definitions, possible causes, and suggested next steps.
  • General troubleshooting tips.
  • What happens if you do not fix an error.
  • How to report a bug.

How to identify an error

Zapier displays a Stopped: Errored status next to any errored Zaps in your Zap history and in the Zap editor. When you select a specific Zap run, you’ll find additional information about the error. You can identify errors in either your Zap history or the Zap editor using AI-powered troubleshooting. This feature can explain the issue, but also provides step-by-step instructions to resolve it.

How to find an error in your Zap history

In your Zap history:

  • Click a Zap run that has a Stopped: Errored status. You will be redirected to its Zap run details page.
  • Find the errored step, then click the Troubleshoot tab.
  • Zapier will use AI to create troubleshooting instructions for you to review.

AI-powered troubleshooting instructions in Zap history

How to find an error in the Zap editor

In the Zap editor:

  • Click on the Zap runs icon in the left sidebar to expand it.
  • In the list of Zap runs, click the arrow next to a Zap run that errored to expand it.
  • Click Go to step. This will expand the right sidebar and auto-select the errored step.
  • In the right sidebar, click the Troubleshoot tab.
  • Zapier will use AI to create troubleshooting instructions for you to review.

AI-powered troubleshooting instructions in Zap history

HTTP status codes

Zapier connects to your apps to receive and send data. When an app's server responds to a request from Zapier, an HTTP status code is sent to Zapier. When an error occurs with your Zap, these error codes can help pinpoint the issue.

400 - Bad Request
Definition

The server could not understand the request due to invalid syntax.

Possible causes

This may happen when there are missing values in required fields, invalid characters in your input, or an incorrectly formatted request.

Suggested next steps

Review these articles:

403 - Forbidden
Definition

The server understood the request but refused to fulfill it.

Possible causes

This usually happens when your app account has insufficient permission to complete the request. For example, you cannot edit a record if you have view-only access.

Suggested next steps

Check your app connection and account permissions:

  • Confirm your app account is connected properly to Zapier and has the required permissions. You may need to contact your app’s administrator for access and permission.
  • Search for the app’s How to get started page in Zapier’s Help Center to find information about how to connect.
404 - Not Found
Definition

The server couldn’t find the resource you requested.

Possible causes

This usually happens when you are trying to find a record that does not exist in the app.

Suggested next steps

Review this article: Fix "Not found" errors in Zaps.

422 - Unprocessable Entity
Definition

The request was well-formatted but contained errors that prevented the server from fulfilling it.

Possible causes

This usually happens when you send data, but it’s in the wrong format, or there is missing data that the request requires.

Suggested next steps

Check that all Zap fields are entered correctly:

You can use Formatter to change data formats or add a default value as a fallback whenever your mapped fields don't send data.

429 - Too Many Requests
Definition

The user has sent too many requests in a short period.

Possible causes

This usually happens when you exceed either Zapier’s or an app’s rate limit. 

Suggested next steps

Review this article: Rate limits and throttling in Zapier.

500 - Internal Server
Definition

The server encountered an unexpected condition that prevented it from fulfilling the request.

Possible causes

This is a generic error message that can be caused by a variety of problems in Zapier or with the app you're using.

Suggested next steps
  • Wait and try again later. Sometimes this error is temporary and will resolve on its own.
  • Check for Zapier issues. Go to the Zapier Status page to see if there are any ongoing outages or scheduled maintenance.
  • Check the app’s status page. The issue could be specific to the app your Zap connects to.

General troubleshooting tips

  • Find a solution in the Community: Browse the Zapier Community for questions and answers from other users. You can also ask questions about specific errors.
  • Learn about common problems: Explore additional articles on how to troubleshoot Zaps.
  • App help documentation: Review the documentation for the specific app in the Zapier Help Center or the app’s own help center. It may contain more specific troubleshooting advice.

What happens if you do not fix an error

Your Zap will automatically turn off if 95% of its runs result in errors in the last 7 days. Learn more in my Zap isn’t running.

If your account is on a Team or Enterprise plan, Zapier will send you an email notification to the account owner and provide a grace period before turning off your Zap. Enterprise plan accounts have a 72-hour grace period and Team plan accounts have a 24-hour grace period.

If you have an Enterprise account, you can override the high error ratio setting for an individual Zap.

How to report a bug

Think you have found a bug? Report it to Zapier Support.

Was this article helpful?
0 out of 0 found this helpful