Real PTE Practice Test Questions Free and AI - PTE Magic

The 9 best to do list apps for Mac in 2021

Automation helps me run my business, Saastronomical, where I help other people automate their businesses. And while automation helps us keep things moving, sometimes things go wrong: we get an error message telling us there’s a problem with our workflow.

When that happens, it’s important to know how to fix it. Here are some of the common errors you might see with your Zaps—the automated workflows you create with Zapier— and how to troubleshoot so you get things back on track quickly.

This post was developed from a session Andy Wingrave gave at ZapConnect, Zapier’s user conference. Watch the session here.

Table of contents:

Zapier lets you automatically send information from one app to another, helping you reduce manual tasks. Learn more about how Zapier works.

How to find error notifications 

Zap error notifications can appear in three places:

  1. In the Zap editor: this is basically when you’re building the Zap, you get an opportunity to see whether there was a success or a failure.
  2. Email notifications: The second place you might encounter an error notification is after you’ve turned your Zap on.  Zapier will send an email to the address on your account, informing you that something has gone wrong with your live Zap and it needs to be investigated. 
  3. Zapier dashboard: The last place we might see an error is within the Zapier interface, specifically in your Zap history. Whenever a Zap is halted due to an error, from your dashboard, you can choose whether or not to replay the Zap. 

Zap editor

Errors often appear in the Zap editor when you’re testing each step in your Zap. (You are testing, right?)

You’ll often see an error message telling you what Zapier couldn’t accomplish and why.

An error message in red during testing in the Zap editor.

When you’re testing a trigger—the event that starts your Zap—you might encounter an error if Zapier could not find a recent entry. For example, if you want a Zap to trigger off of a new Airtable record in a view, it may not work if that specific view is empty.

Email notifications

These messages come into your email address when something goes wrong with a Zap that has previously been running. These are warnings that you should head into your account and take a look. 

The email will contain some key information about the error:

  • Which Zap caused the error. 
  • The error message itself.     

This can help you identify what could’ve gone wrong and you’ll have the context needed to troubleshoot your Zap.

You’ll also see an orange Fix My Zap button, which will direct you to the Zap editor to fix the issue. We’ll get to that piece later. 

An example of an email notification whenever a Zap encounters an error. The email message includes an orange button that says, "Fix My Zap."

Want to get Zap notifications elsewhere? Check out this guide on how to use Zapier Manager to automate your Zap monitoring.

Zapier dashboard

In some instances, Zapier will hold a Zap run if more come through than usual. It’s a safeguard to ensure that you’re not burning through your task usage for the month

A yellow alert next to a Zap notifies the user that 14 Zap runs were held.

If a number of Zap runs are held, you can also replay them in bulk or choose individually which ones you want to run. 

Learn more about replaying failed Zap Runs.

Common error types

When you’re troubleshooting, you’ll often see a few types of errors. In the error message, you’ll usually see a three-digit error code. The most common ones are 4XX errors and 5XX errors. 

4XX errors

4XX errors are typically issues with Zapier. It’s often caused by data you’re trying to send to an application. You’ll usually come across these four types of errors:

  • 400 Bad Request: The app you’re sending data to doesn’t understand the request. Usually, this shows up when you try to map a value in the Zap editor to the wrong field type. For example, sending a true/false (boolean) value to a date field. 
  • 401 Unauthorized: Reauthorize the application.
  • 403 Forbidden: The account is connected properly, but the action you’re attempting to perform is not allowed.
  • 404 Not Found: The item doesn’t exist.

5XX errors

5XX errors, on the other hand, are server errors.  This indicates that there’s an issue with the application itself. It doesn’t understand the request or it hasn’t been configured correctly to receive the request. 

When this occurs, you should reach out to the app developer and find out what’s happening. 

Remember, when you’re not sure about any of these errors or what’s happening, head on over to the Zapier documentation and the help pages to identify the best course of action for each error.

Learn more about 5XX status code errors.

Troubleshooting checklist

The best way to avoid many of these error messages in the first place? Troubleshoot before you turn on your Zap. 

I used to have a manager who often said, “measure twice, cut once.”  What he meant was that if you check your work and what you’ve created, you can avoid errors that would cause issues in the future.  The same is true when you make a Zap: if you ensure everything is set up properly before turning it on, you can spot—and fix—problems before they derail your automation. 

We’ll walk through each of the troubleshooting steps you can take to fix a broken Zap in more detail.

Troubleshooting steps: 

  1. Check that all fields are entered correctly
  2. Check your app connection and account permissions
  3. Read help docs for Zapier and the app

1. Check your fields

One of the most common mistakes when creating Zaps is incorrectly entering data in fields. There are several field types, each of which tell Zapier how to handle the data you place there.

Field types need to match the data type. You can’t pair a static plain text value that says “January” with a date field, for example, because Zapier won’t understand it. 

Learn more about different field types in Zaps.

One of the common field types people make mistakes with is dropdown menus. 

Here’s an example: We’re trying to create an invoice in QuickBooks and add a customer to it. Here’s a dropdown menu with our customers. We want Zapier to dynamically set the customer based on what happened in the previous step—but we’re presented with limited options. 

A dropdown menu in the Zap editor listing QuickBook customers.

Dropdown menus understand IDs, not text. Note the tiny grey number underneath each customer. However, most people make the mistake of entering text. This will fail because Zapier is expecting a specific value or ID instead. 

A box highlights the Customer field when setting up a QuickBooks action in the Zap editor. There is text typed in the dropdown field.

So how can we dynamically set our customer? Instead, click on the Custom tab, and select the value you want to use from a previous step in your Zap. Now you’ll pass your dynamic data every time your Zap runs. 

A yellow box highlights the Custom tab in the Zap editor. This allows you to dynamically set values in your Zap when dealing with a static dropdown menu.

The “Custom” option lets you dynamically map values where you’d otherwise have to select just one. Learn more about how to use it effectively.

If you can get your head around different field types, you will avoid many mistakes in the future.

I always recommend testing and reviewing your Zap. Click on Test and Review instead of Test and Continue to get in the habit of reviewing your data. You can catch mistakes early before they escalate!

2. App connections and account permissions

The next step in our troubleshooting checklist is to check your app connection and account permissions. 

First, make sure your app connection is up to date. Connections between an app and Zapier will expire after a given time, such as after a year. You can reconnect your account in the Zap editor. If the connection expires, there will be a red message prompting you to connect it again. 

Connecting an app account in the Zap editor. The app connected here is QuickBooks Online.

If you’ve connected the wrong account—for example, if you used a testing account to create your Zap but forgot to connect the primary account to the Zap—you can also click + Connect a New Account to quickly add it. 

Then, check your app permissions. Some apps require certain permissions for a trigger or action. For example, some integrations like QuickBooks Online require you to have admin permissions to use it. 

To figure out which permissions you need, check the Zapier help docs for the app you’re using. 

3. Read help docs for Zapier or the app (or both)

There are a few places where you can access help docs for Zapier or a specific app. 

You can find the help page for a specific Zapier integration by searching for the app in the App Directory. On the integration page, click on the Help tab to view the available help docs. Clicking those links will open up the relevant document in our Help center.

The Zapier integration page for QuickBooks Online. App-specific help docs are located in the Help tab for every app in Zapier's App Directory.

You can also access Zapier’s main Help center by clicking on Resources in the top menu, and then selecting Help center

Zapier's Help center location is highlighted in the top menu in a Zapier account. The Help center is located in the Resources tab.

You can search for the specific issue, or navigate the Help center based on topic. 

The front page of Zapier's Help center. A search box is highlighted.

Troubleshooting within your Zap history

If you’ve tried those steps and your Zap is still encountering errors, you can troubleshoot the issue based on your Zaps’ previous runs. You can do so in your account’s Zap history. 

How to read your Zap history

Your Zap history is just that: a history of every time your Zaps have run. You can access your Zap history in the left-hand navigation window of your Zapier account. 

In your Zap history, click on the Zap runs tab. You can search for a particular Zap run by a date range, the Zap associated with it, the apps involved, and more. 

A list of stopped Zap runs in an account's Zap History. Each stopped status has a red hand next to it.

There are three core statuses that we should be aware of when troubleshooting the Zap history: stopped, waiting, and holding.  

  • Stopped: Stopped statuses include errored tasks—where the error isn’t expected—or a halted task, where an error was expected and the Zap was stopped from proceeding. Only error tasks will turn a Zap off automatically.  
  • Waiting: This status could occur when you’ve added a delay step in a Zap or your Zap is waiting to be tried again because you’ve enabled Autoreplay.
  • Holding: This could be any number of account-related issues, such as high task usage, an account connection issue, you don’t have enough tasks for your Zap to run, or you haven’t paid your Zapier bill.  

How to investigate the Zap run

When you’ve identified a Zap run that’s encountered an error, click on it. 

Within this account's Zap History, a box highlights a Zap run with an error.

The first thing you’ll notice at the top is the Replay Zap run button. This allow you to play this specific Zap run again. Before we do that, scroll down.

A box highlights a blue button that says Replay Zap run. An orange arrow points down, with instructions to scroll down the page.

Depending on how complex your Zap is, it may be several steps down before you find the error. It will have the red icon with a hand, indicating that this step was stopped, along with an error message.  

In this example, the error message in step six says “nothing could be found for the search.”  Remember: that’s a 404 error. 

An example of an error within the details of a Zap run. The error message displays in Step 6 of this Zap.

Navigate between the Data In and Data Out tabs. Data In contains the information passed through this step. Data Out is what the application returned.

Boxes highlight important areas to pay attention to when viewing a Zap run in detail.

In this example, we can see that our application, Airtable, couldn’t find anything in the search. 

The Data Out tab is selected in Step 6 of this Zap run. An error message says, "Nothing could be found for the search."

If you’re confident you know what the problem is, or want to investigate further, click on Edit This Step. It will direct you to the specific step in the Zap editor, where you can perform all the troubleshooting steps.

A box highlights a link that says, "Edit This Step." This link is in each step of a Zap when viewing a particular Zap run.

If you’re unsure of how to fix the issue, click on Documentation, which will take you to the application’s specific documentation. Get Help will put you in touch with Zapier’s amazing support team. You can also turn to the Zapier Community for help. 

A box highlights two blue buttons, which directs the user to help docs and contacting support.

Zapier status page

 Another resource available to you is Zapier’s status page. When you visit status.zapier.com, it will provide you with updates in three areas: system, app status, and incident history. 

  • System metrics: This covers trigger reliability and response time.  Essentially, whether there any issues with Zaps triggering.  
  • App status: Covers issues with specific applications.  
  • Incident history: Highlights any major instance within Zapier.  
The Zapier status page. A green alert says "All Systems Operational."

You can also subscribe to status updates for up-to-the-minute notifications when there’s an incident.

Keep calm and troubleshoot on

When you need to troubleshoot a Zap, don’t panic. Everything will be okay. Remember to follow the troubleshooting order of operations. If all else fails, you can find a solution in Zapier’s Community, contact Zapier support, or hire a Zapier Expert.

Andy Wingrave is a Zapier-certified Expert. He’s the chief automator at Saastronomical, through which he offers 1:1 consulting and assistance creating Zaps people need to save time and money. You can watch his ZapConnect 2021 session, Troubleshooting your Zaps, here.