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 hit 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, a “200” code means that a Zap ran correctly, so this code is usually “behind the scenes” when your Zap runs successfully. 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 and go through all the steps of the Zap to make sure that the correct account is selected and working, the correct fields are mapped, and that the Zap tests successfully.

400 Series codes#

Generally, when you see this error, it means that information is not being accepted when the Zap is communicating with the applications inside of your Zap. This often is information in a required field or login/authorization information.

  • 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 each step of 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 going through each step, you'll want to make sure that any hardcoded information is typed correctly, and that all required fields have appropriate information in them.

Common 400-series codes you might see include:

  • 401 - often points to invalid credentials. The best option here is to test your connected account or step 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.
  • 410 - often 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.
  • 429 - often points to “too many requests.” This can mean that the Zap is asking for or sending the application information too frequently within a time frame. Often the fix is to change the Zap to trigger on fewer items, or to add a filter step if your workflow needs one.

500 series codes#

  • 500 series errors (501, 502, etc) - these generally point to an issue with a delay in the connection between Zapier and the application, and are often called timeout errors. These kind of errors 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. If you run into one of these errors, you'll want to check if it happened to a trigger step in your Zap or an action step in your Zap.
  • 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.
  • 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.

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

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, send us a message here, and we’ll be happy to help.

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