Troubleshoot errors in Zapier

Zapier works by connecting to your apps and services to receive and send data. When an app's server responds to a request from Zapier, a HTTP status code is sent to Zapier. You might see an error code when you create a Zap or look at your Zap history.


General troubleshooting tips

Take these steps to troubleshoot errors you encounter in Zapier:

  • Turn the Zap off, then on again. This resets the Zap and can resolve some errors. 
  • Check that all Zap fields are entered correctly. For example, check that all required fields are filled and that you used the right data formats for each field type. You can use the Formatter tool to change data formats if needed.
  • Check your app connection and account permissions. Confirm that your app account has been connected properly to Zapier and that you have the required permissions for the Zap to work. Search for the app’s How to get started page in Zapier’s Help Center to find information about how to connect.
  • Wait and try again later. Some errors are temporary and will resolve on their own. 
  • Load a new trigger sample, then set up your action steps again. If your trigger isn’t sending data, it could be that the trigger fields have changed. Double-check that your mapped fields are also up-to-date. 
  • Check your filter and path conditions. Ensure you’re using the correct filter and path rules.
  • Read the app help docs. Search for the app in Zapier’s Help Center to learn more.
  • Find a solution in our Community. Browse the Zapier Community for questions and answers from other users. Ask questions about the specific error you’re encountering and learn more about the apps that you’re using.


Error codes & messages

HTTP status codes that begin with a 4 or 5 (401, 504, etc.) are error codes.

400-series error codes

Error codes between 400 and 499 are client errors, which happen when the error occurs on Zapier’s end.

500-series error codes

Error codes in the 500 series are server errors, which happen when an app’s server is down or experiencing other issues.

Other error codes

You may see a status code that’s not included in the list above. These are non-standard status codes and are likely specific to the app you’re connecting to Zapier. If you encounter one of these errors, reach out to the app’s support team for assistance.

Other error messages

You may also encounter an error message that doesn’t include a status code at all. Search for the error in Zapier’s Help Center or the Zapier Community for more info. If you still need help, reach out to the app’s support team for assistance.


I want my Zap to continue running even when there are errors.

Your Zap will automatically turn off if 95% of its runs result in errors in the last 7 days. If you have a Zapier for Companies accounts, you can override the high error ratio setting for an individual Zap.

  • Open your Zap in the Zap editor.
  • In the right sidebar, click Settings.
  • In the Error ratio override section, select an option for this Zap:
    • Turn off if errors occur: the Zap will automatically turn off when it surpasses the high error ratio. This is the default and recommended setting.
    • Keep running if errors occur: the Zap will never turn off, even if it surpasses the high error ratio.
miscEye icon Note

You must have edit access to the Zap to override the high error ratio setting.

If you need additional help with errors, contact Zapier Support.

Was this article helpful?
3 out of 25 found this helpful