Translating Errors#

Why did my Zap fail to run successfully?#

Most of the time, your Zaps run without any problems. But occasionally, your Zap might fail to run as you expect and return an error code, an error message, or both.

What is an error code?#

If a Zap cannot complete successfully, often the Task History for the Zap will display an HTTP error code and usually an error message. These error codes can give insight as to where the problem originated and how to troubleshoot it.

The codes that are used are standard across the internet, and you may recognize some codes from other places online. For example, maybe you’ve seen a 404 returned before when a webpage couldn’t be found. Google 404 image You can check out all HTTP error codes and learn more information about them here.

Basic Troubleshooting for Any Errors#

If you encounter an error on your Zap, the first thing you'll want to do is to go to the step in your Zap that shows the error. Then make sure that the correct connected account is selected and working, the correct fields are mapped, and finally retest the step. If you receive an error message or error code here’s what some of those can often mean.

400 Series codes#

This usually means that we were able to connect to this app, but they indicated a problem with what the Zap was asking to do. This could be related to the connected account having a changed password or limited permissions or with necessary values for this step being missing or in the wrong format.

A good place to start with 400-series codes is to make sure that the connection to the application is set up correctly. You can go to your Connected Accounts page in your Zapier account and click “Reconnect” to reset the connection to the application. During this process, you'll want to make doubly sure that login information and URLs are all spelled and formatted correctly.

You can also go within the Zap itself. Go to the effected step within the Zap again and use the “Test Step” option to retest the step. This will often bring in any changes that have been made which could produce the error. Also, while you're testing the step, you'll want to make sure that any typed information is correct, and that all required fields have the appropriate information in them.

400-series codes you might see include:

  • 400 - This usually happens when your Zap is missing a required field or a field value isn't in a recognized format. For example, if a field in an action is expected to be an email address, but the value given is a name, that might result in an app returning a 400 error.
  • 401 - This usually happens when we can't connect to your account for an app or service because your password was changed or Zapier's access was revoked. Often the best option here is to try reconnecting the app account in the Zap and verify it still shows a “Success.” You can also go to your Connected Accounts page and click “reconnect” to reset the connection to the application.
  • 403 - This usually happens when your connected account doesn't have permission to complete this step. For example, your account might have permission to create new contact records, but not edit existing contacts. You should contact the administrator for your account and make sure you have the required permissions for the step.
  • 404 - This usually happens when a field value used in this step is missing or we're unable to find the information on your connected app or service. For example, a Trello board may have been deleted that we were searching for. Start by making sure that the information exists and that the field values used in this step are entered correctly.
  • 405 - This usually happens when the app or service is experiencing a problem. Please contact our support for help fixing this error.
  • 408 - This usually happens when the app or service you’re connecting to is too busy or temporarily unavailable. Try waiting a few minutes and try again. If the problem continues, please contact our support.
  • 409 - This usually happens because the record that you are trying to update or use is already in use or being updated somewhere else. It’s best to wait and then try again once it becomes available.
  • 410 - This usually refers to data that is missing. You'll want to go through your Zap and make sure that fields - especially any custom fields - are selecting options that exist on the account, in case anything has been deleted/renamed/moved. For instance, searching for a Trello card that no longer exists.
  • 414 - This usually means the URL being sent was too long. If you're using Webhooks, check to make sure you're not adding too many values to the webhook URL. If you're using a different app or service, please contact our support for help fixing this error.
  • 415 - This usually means the app was expecting a file of a certain type, but received a different type. It’s good to start by checking any file or image being sent are the correct file type. For example, be sure you're not trying to upload a Word doc when only PDF's are allowed.
  • 429 - This usually means that the app has made “too many requests.” This can mean that the Zap is asking for or sending the app information too frequently within a time frame. Some common fixes include changing the Zap to trigger on fewer items, adding a filter step if your workflow needs one, or upgrading your app account to allow more requests.

500 series codes#

Generally, when you see a 500 series errors (501, 502, etc) - these point to an issue with the application’s server that Zapier is trying to connect to. These kind of errors can often resolve themselves within a short period of time. For example, if the application is undergoing server maintenance, or if the platform is currently overloaded with API requests from all its users, this may result in a 500 series error. 500 series errors may require a little patience, as there is often not much that can be done to resolve the error beyond waiting for the delay to resolve itself.

500-series codes you might see include:

  • 500 & 503 - These are the most generic 500 series codes and can happen when a server is down, experiencing other issues or when the server doesn’t know what else to return. We suggest checking the App's status page and trying again in a few minutes. If the 500 error was on your Trigger app, no further action is needed. Your Zap will run again the next time we can successfully poll. If the 500 error was on your Action app, you can go to your Task History and try replaying the failed Task. Usually timeouts are temporary so replaying later often solves the issue.
  • 504 - Some of the most common causes of this are when working with large datasets or trying to upload a large file. If your Trigger returns a 504 then it’s likely that there is more data (i.e. a large spreadsheet) than we can get in our timeout window. Normally, the only way to resolve this error is to reduce the amount of data that is being Triggered from or uploaded.

Other Errors#

"Missing", "Empty", "Not Found" errors - These errors indicate that the action your Zap wanted to take did not have all the data needed. The most common cause of those errors is that a required field is empty. It could also mean a dropdown option you had selected in your Zap no longer exists. Check your Zap to make sure all the data is up to date.

"Unauthorized", "Could not Connect" errors - These errors likely mean we cannot connect to your account with the provided information. We suggest reconnecting that account to see if that fixes the problem.

"Timeout" errors - If you see the word timeout in your error message, it means the request took too long and ran out of time. This could happen if the connected app’s server is running into trouble and it might fix itself. If it doesn’t it might be that the data you are trying to pass is too big to handle. Check your Zap and Task History to see if you are trying to pass a particularly large file or a lot of data.

"gaierror(-2,)" - We usually see this if we are unable to resolve your hostname (URL). Re-check the URL you are entering into your step and make sure it is something you are able to access from the outside world (external to a local network).

Seeing another type of error message not listed here? Try searching for the name of the app you're running into issues with and check out the associated "Common Problems" article.

Can't find the error message?#

If you require further assistance, contact our support, and we’ll be happy to help.

↑ Was this documentation useful? Yes No (Suggest Edits)
Get Help