How to troubleshoot errors in Zaps

Review issues 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.

Review issues in the Zap editor's Zap runs section

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.

Tip

If an outage affects an app used in your Zap, you will see a notification in the affected step. The app's team typically resolves these outages. Contact the app directly for more information or support.

Review issues in the Zap editor's Status section

The Status section in the editor's left sidebar notifies you when there are any issues with your Zap that will prevent you from publishing it. It appears when you: 

• Edit a draft of your Zap.
• Encounter an issue with your Zap after publication.
• Should test steps in your Zap.

To review issues:

1. In the editor, click the Status icon in the left sidebar to expand it.
   • The number icon indicates how many issues the Zap has.
2. Affected steps will display an issue notification box.
3. Click the issue notification box to open the affected step.

Issue	Definition	Icon	Example
Warning	A step has an issue that will prevent you from publishing your Zap.		You left a step before completing it.
Error	A step has an issue that occurred after you attempt to publish your Zap.		You need to reconnect your app.
Info	There’s additional info about a step that you should know about.		The app you’re using will be deprecated.

Tip

Error, warning, and information icons also appear in the top menu of the affected step and in the sub-section of the affected step where the issue is occurring.

Review issues in the Zap’s HTTP log

Understanding your Zap’s HTTP log can help you diagnose issues with your Zaps. Though it delves into technical details, the HTTP log is an accessible tool for identifying Zap issues.

To find a HTTP log for a Zap step:

• 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 Logs tab.
• Zapier will display the:
  • HTTP status code
  • Error message
  • API endpoint
• Click the error log to open a dropdown menu.
• In the Request information dropdown menu, you can find detailed log, including:
  • HTTP method
  • API endpoint
  • Parameters
  • Headers
  • Request body

Use this information to identify the cause of your Zap’s error.

Note

If the step errored as it was missing required information to complete the step, logs will not be available.

Tip

If you cannot read the log, copy and paste it into an AI tool. Then, ask the AI to explain the potential causes for your app's error response.

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:

• Zap field won't accept your data
• Fix "Required field is empty" errors in Zaps

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.

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.

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:

• All required fields have values
• All values use the right format for each field type.

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

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.

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.