Troubleshooting Your Zaps#

There's a wide range of reasons that a Zap can come back with an error. We do our best to provide actionable error messages, but sometimes there's too many potential problems or an app's error messages are vague, leaving you to wonder what went wrong. Here's some steps you can take to get to the bottom of the problem:

Check Your Error Message#

We have a guide on common error messages here.

Check Your Task History#

Your task history is a log of all the tasks your Zap has attempted on your behalf, you can access it from this link or from your dashboard. While the task history won't show a record of tests made when configuring your Zap, or errors in connecting to your trigger, it's invaluable to identifying errors when your Zap tried to complete its action.

Two Task History Items

You can click on the "Data In" and "Data Out" buttons for both your Trigger and Action apps to see what data we received and sent on.

See your tasks Data

For more information on using the Task History to debug trouble with your Zap, please see our Task History Guide here.

Check Your Zap#

Many errors can be corrected with just a small change to the configuration of the Zap, especially the Action template. We go over some common scenarios here, but here's some things to look out for in general:

  • Are your filters going to filter too much, or not enough? Reference this guide for more details on filters.
  • When mapping fields for the action, have you used the + button to include data from your trigger? Whatever you manually type in will be sent through every time your Zap triggers.
  • When mapping fields for the action, are all the required fields filled in and are you using fields that will have data in them when your Zap triggers?
  • If you're using the "Use a Custom Value" option in a dropdown, is that sending data that the action will understand?

Check Your Accounts#

Sometimes your Zap is working successfully, but it may be creating data in a place you weren't originally expecting. Especially if you're creating something that belongs under another object(like how a Task may belong to a specific Project), check your Zap to make sure the destination you've chosen in your Zap matches where you're looking for that data in that app.

Check the Docs#

Some errors are a result of oddities in how a particular app behaves. We do our best to document those in our Service Documentation, so check that out for the app involved to make sure there's not an easy fix waiting for you!

Common Problems#

A Required field is empty#

When mapping action fields, you'll see the fields that the action app is telling Zapier are required to perform that action.

Required Fields

Make sure that the fields you choose to include from the trigger app will always have data in them. If they are ever empty, then the Zap will very likely create an error.

If you're okay with trigger data not always being included, there are a couple potential workarounds:

NOTE: These workarounds may not apply universally: some apps have more strict requirements about the values that can be used, as well as varying degrees of acceptance for duplication. Also, if there is more than one required field where this is an issue, the 2nd workaround will require several Zaps to account for all the potential outcomes. We don't recommend that 2nd workaround if there's more than one required field with a risk of empty data in the trigger.

Dropdown choices are empty#

Dropdowns show possible values to be used within fields.

Often the choices are dependent on some specific criteria, like the value of a previous dropdown. Sometimes choices are dependent on the account you've connected because choices may be dependent on your account's permissions.

If you're seeing empty choices, make sure the account you've connected has the necessary permissions to show all of the desired choices, and make sure that any criteria you have set up in your Zap that may be filtering out choices is set up appropriately.

For example on the screenshot below this "list" dropdown doesn't have any options, as I don't yet have any lists on that particular Trello board:

If I add a list to that board on my Trello account, that will then appear in that dropdown on my Zap template like this:

Filters are not working as intended#

If you use any filters in your Zap, especially custom filters, make sure that you understand the logic those filters are using. There are two easy ways to check on your filters:

  • Your test will show if your filters would stop your sample: LINK
  • Your task history will show tasks stopped by your filters in gray: LINK

In both instances, you should see a reference to which filter(s) is stopping that task from proceeding. Here are a couple other common issues people run into with filters:

  • If you have multiple filters and want them all to apply to each task, make sure to force them to use AND logic. You can create AND filters using the "Add AND Filter" button under each custom filter.
  • If you use the "(text) Exactly matches" condition, sometimes that will filter more than you expect. Unless there are multiple values coming through for the field your filter is monitoring, you should use "(text) contains" instead to avoid that problem.
  • If you use AND filters and they are both looking at the same field, it's more likely that your Zap will be filtering every triggered task. Unless you are absolutely sure there is more than one value you need to filter for that field, multiple AND filters for the same field should be avoided.
  • The value portion of the filter has a 255 character limit.

Times are incorrect for events#

If your Zap is creating an event, or taking a date from an event to send somewhere else, here's some common fixes that can avoid errors:

  • Make sure you have your time zone settings set in Zapier. It's one of the User Settings you can adjust at this link. If your time zone isn't set, then you may see events created by your Zaps that are off by a consistent number of hours.
  • If you are using Google Calendar and you use DD/MM/YYYY as your date format, you'll have to make an adjustment in your Zap. Google Calendar only accepts MM/DD/YYYY values through their API, so in order to create events on the right date, your Zap will need dates in the MM/DD/YYYY format.
  • If you need to create events that are intentionally offset by a certain time or date (e.g. create an event for a date + 7 days), you can use our datetime modifiers to accomplish that:

Using Custom Values in Dropdowns#

Sometimes you may find you don't want to use a fixed values in a drop down but using a custom value can cause errors if it doesn't match up with what your app is expecting. To avoid that please follow our guide here.

What Does It Mean If Your App Is Tagged "Deprecated"#

If you notice the app on your Zap is tagged "Deprecated" that means that the version you are using has been deprecated and a newer version of the app is available.

What to Do with Your "Deprecated" App#

If your App has been deprecated you will need to switch to the new version as soon as possible. We will send you an email to let you know when the deprecated version will be removed so you know when that will happen.

If you don't get your Zap updated before the date we specified in the email we sent you, your Zap will turn off automatically and we will send you another email to let you know.

To switch to the new version, simply select the app version on your Zap that does not specify "Deprecated". When you do this, your Zap will turn off. You will then need to reselect any options, remap any fields and retest your steps. Once you have done that, you can turn your Zap back on again.

Note, if you Zap uses a Delay step if you have any delayed tasks waiting those will not be able to run once you have switched to the new version. You'll want to either allow those to run before switching or plan to re-trigger them once you have migrated!

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.

Common Problems#

Why Isn't My Zap Triggering?#

Sometimes you might find that your Zap doesn't appear to be automating anything - that's not great! There are a few reasons why this might be happening - this guide will walk you through tests you can do and common problems that might be affecting your Zap, so you can get your Zap fixed right away.

The first thing to do is make sure the Zap is on and then search for the item that should have triggered the Zap in the Task History for that Zap. If you don't see it, continue to Troubleshooting Trigger Steps right below. If you see the record there, head on to Troubleshooting Action Steps.

Troubleshooting Trigger Steps#

A trigger is what will start your Zap, and send new information into the Zap. Often, it's this step that is causing issues, because the trigger app might not be sending data to us. Running through the options below are good ways to eliminate or identify common problems that affect Zap triggers:

  • As a general rule, a trigger that is set up for a Zap will only trigger for newly created records, or if the trigger has the word “updated” in its name, it will trigger for updates to records. This means that existing content will not trigger a Zap when it's turned on. For example, if you have a trigger for “New Contact,” the Zap will only trigger if the Zap is on and a new contact has been added. It won't trigger on contacts you already had in your contact list before the Zap was turned on. If you need to import existing data, you can try this workaround.
  • Try turning the Zap off and then back on. This is a very simple first step, but can sometimes refresh the connection between the Zap and the triggering application. Then, try adding a new record that should trigger off the Zap to test if it works.
  • Test your connection with the trigger step from your Connected Accounts page in your Zapier account. This page will let you click the “Test” button to make sure the connection is still working. Clicking “Reconnect” is the best way to refresh this connection if it doesn't seem to be working.
  • Reselect any fields in your trigger options page on the Zap, making sure to go from top to bottom if there are multiple options. Sometimes, the options you've selected have been changed in the trigger app, which can sometimes cause a disconnect between what currently exists on your app and what Zapier is looking for in the application.
  • If your trigger step has any options that limit what it triggers on, make sure the new records you're looking for match those options perfectly. For example, if you have a “Tag added to contact” trigger and you've set it to look for the tag purchased-book, make sure that the tag added to the contact doesn't say something different, like purchased-song.

Troubleshooting Action Steps#

The action step is the action we will perform once we get data from the trigger app. If you see the record in Task History but not in your action step, that means that there was a problem with how the action step was receiving information. Try the options below to narrow down what the issue might be:

  • If you have a filter step, make sure your filter conditions are correct. Sometimes editing this step further will allow you to get the records you want into your action app. Make sure AND/OR logic is how you'd like it to be, and that the spelling and capitalization is correct.
  • If you notice an error message (these are in red boxes), try our tips on troubleshooting errors.
  • If you see a message indicating that a record was not found, double-check inside your action app to make sure that record exists in the way we were searching for it in the Zap.

Two Way Syncing#

Zapier does not support two way-syncing right now, for any App. This extends to the idea of keeping records up to date after the initial Trigger and Action occurs (it is not currently supported). Think of Zaps like one-way, one-time actions.

In certain scenarios, you can "fake" two way syncing by setting up two different Zaps that perform opposite actions of each other. However you must be careful not to create a Zap Loop. Check out this guide for more information on how to avoid Zap loops.

Update Items and Keep Items in Sync#

By default, Zapier does not keep items in sync after they have been run through a Zap one time. Think of Zapier like a one-way one-time pipe right now. However, if you're using Zapier integrations that have update-based triggers and actions, it's possible to set up a second Zap to capture updates. This is only true for apps that support updates; apps that only have create-based triggers and actions will not capture updates.

You can email us if you have specific questions about an app. Usually you can tell by creating a Zap and seeing what actions are available for a given app.

Sample Data does not Load#

When building your Zap, you may have difficulty loading data from the trigger app. Here are some common causes:

  • The account connection for the app is not correct. Try testing that connection in the trigger portion of your zap, or even re-adding it in that step to see if you have improvement.
  • You don't have a recent sample. Perform the trigger in your Zap and then retest your trigger. For example if your trigger is Typeform's 'New Entry', submit an entry to your form then retest your trigger.
  • Make sure filters aren't preventing your data from loading. For example, if you have a filter to only trigger your Zap on Gmail emails with a certain label, make sure there are recent emails with that label.
  • If your Zap is an Instant trigger, you need to add sample data. For Instant triggers, because they push the data to us, you need to create a sample in the trigger app after your Zap starts looking for sample data.

Zap doesn't Move Existing Data#

Zaps will not be able to see data that was created before your Zap was turned On, they are meant to trigger off data that has been newly added.

One workaround is if you are able to obtain a data export file with all of your data from some App, probably in comma-separated values format (CSV file). With a CSV in-hand, you can semi-manually copy records into a Google Spreadsheet to trigger a Google Spreadsheet Zap. Be wary of rate limits. You can check out this guide for more information.

Fields do not Match#

Sometimes apps treat the same type of data in a different way. For example, some apps separate First and Last name into multiple fields while others group them together. Here are a few ways to add and manipulate data in your Zap:

Avoiding Zap Loops#

If you have two Zaps that mirror each other, you can potentially end up with "loops" where your Zaps trigger each other repeatedly. To help with this, check out this guide on avoiding Zap loops.

Typing into Dropdowns#

In your Zap you have the option of inserting a custom value in dropdowns that have populated values for you to choose from. Many times, these custom values are the causes of errors, so try using the populated values instead if you do get errors when using the custom values.


Unicode errors#

If you get errors relating to Unicode characters, please contact us.

Can't Connect a Second (Alternate) App Account to Zapier#

There are a lot of cases where users have 2 different accounts with a particular app (e.g. two email accounts with Gmail). In Zapier, you can connect as many accounts as you want (with rare exceptions). That being said, we sometimes get these questions:

  • Why can't I connect a 2nd account for my app?
  • Why does it always add my original app account when I try to add another account?

Usually, what happens here is that you currently have an open session with an app, i.e. you're currently logged in to the account. Therefore, Zapier uses that logged in session when adding a new account.

To get around this, follow the steps below:

  • Open an incognito window in your browser.

Incognito window example

  • Login to Zapier using that incognito window.

Zapier Login page example

Screenshot of Connect a New Account modal

  • Since you're in incognito mode, there would be no open sessions/cookies for the said app. This should force the popup login to appear for that app.
  • Add the correct login details for the 2nd app.

Viola! The 2nd user login details should be added now. Don't forget to rename the connection using the pencil icon to help identify the new connection.

Important to note: Even Incognito windows will hold on to your session information. If you go on to connect another account with these Incognito windows still open, it'll connect the same account you just connected! Close all open Incognito windows and start over again to connect your next account.

Still having trouble?#

This link has more Zap issues that may help get things working for you!

Rate Limiting#

Zapier Throttling#

For users on free plans and free trials, if your Zaps attempt to perform too many tasks in a short span, you'll receive an error that the Zap has been throttled. That limit is approximately 200 attempts every 10 minutes window per zap.

Throttling from Other Services#

Some other services have API limits and throttling mechanisms of their own. To distinguish between these errors and Zapier throttling errors, look for "Zapier" in the error message. We do not throttle users without using our name in the error.

Flood Protection/Held Items#

If you have a large number of items (100+) that trigger in a Zap at once, Zapier holds them for you and sends you an email requesting your confirmation. This helps prevent a significant number of tasks being performed by mistake, which helps keep your task usage down and prevents tedious work correcting those unintended tasks in the action service.

When released these tasks will be drained the rate of 1 per second. So 1000 tasks would take a little over 15 minutes to clear out after releasing.

Note: Instant triggers are not subject to flood protection, as each item is sent to the trigger individually.

Webhook Throttling#

  • Each users' webhooks are subject to a collective 429 status code rate limit after 10,000 requests in a 5 minute window. This includes subscription webhooks or REST Hooks.
  • Each individual webhook (both legacy and current) route will return a 429 status code after around 30 requests per second to encourage a smooth delivery of hooks vs. massive bursts. This includes subscription webhooks or REST Hooks.
  • Legacy webhook routes without the user ID in the URL will return a 429 status code after 1,000 requests received in a 5 minute window (this is per webhook route). This includes subscription webhooks or REST Hooks.
  • During heavy periods of sustained webhook activity - we may return 200 status but still delay the processing of your webhooks by several minutes.

If you wish to enforce proper delivery of webhooks - please retry delivery on anything besides a 200 status code from Zapier and use an industry standard exponential backoff interval for retries.

App Throttling#

When using an invite-only app, you may encounter an error like Dev app App12345API (AppNameHere) throttled (100 script executions per 30 seconds), contact support. This is due to a built-in limit for preventing spam for non-public apps. Once the app has gone public, this limit on script executions for the app will be lifted.

Working with Files#

What do you mean by File?#

When we reference files on Zapier, we mean the actual file object, and not a text field describing the file. For example, a file would be a photo itself, a field describing that file might be the Name, or the URL for that photo.

These guidelines are generally applicable to all apps that support files. For any details specific to a app, check that app's documentation.

Pulling files from the Trigger#

File placeholders are usually identified as "file" or "attachment" when mapping fields in the action.

File fields

You can only place these file placeholders where there the action app will accept a file object. Those fields contain a document icon for easy reference.

Document icon

Placing a file in the action#

When the action of your zap involves creating or copying a file object, you have two options:

  • You can include a file object from the trigger

File object to File object

  • You can include regular text from the trigger. This will result in a text file being created with the data from those fields.

Note: This may result in an error for some apps. We can't guarantee that every app will accept that input as a text field.

Text to file object


There are two types of "deduplication" on Zapier. One for Triggers and one for Actions, respectively.

Trigger Deduplication#

Zapier relies on a few methods to make sure that your Zap does not trigger multiple times for a single "new" item.

The way Zapier does this is generally by polling, looking for new items every few minutes (your plan's "syncing interval"). Zapier stores an identifier for each item seen so that the Zap never triggers off of that item again. The first poll after turning a Zap on we only store the identifiers and don't trigger on any of them.

If you have two Zaps looking at the same Trigger (for example, two Zaps which trigger off the same Wufoo form) both Zaps will be triggered by new items. Deduplication happens on a per-Zap basis.

Note: certain apps use webhooks ("instant") which avoid the need to deduplicate all together, the rest of the information about Trigger deduplication here does not apply for instant Triggers.

Deduplication has several important ramifications you should be aware of:

  • Once Zapier has seen an item for a Zap, it will never trigger again even if the item is updated in the future.

  • Custom Filters are applied after deduplication happens. So you can't use a custom filter to trigger when an item changes. For example, a #hashtag applied to an Evernote title one day after the note was originally created would not work.

  • Trigger Filters are applied before deduplication happens. You can use regular filters to catch "changes". For example, using the "new note" Evernote trigger and choosing a specific tag to watch via regular filters would trigger even if you applied the tag one day after the note was originally created.

Steady State Postprocessor#

The following Apps and Triggers have a special "steady state" post-deduplication process applied. Normally a new item will Trigger a Zap as soon as Zapier first sees it. However for certain things, that is undesirable because you might still be typing into your Evernote note, for example, when Zapier first detects it.

The steady state postprocessor will wait to Trigger a Zap until the item has stopped changing across one polling interval ("syncing interval").

  • Evernote New Notes
  • Trello New Cards
  • Magento New Sales Orders

Action Deduplication#

Depending on the app, that can result in several outcomes if your zap is trying to create data already in that app:

  • Duplication: Some apps allow for duplicates and therefore the zap will create those duplicates.

  • Errors: Some apps will return an error message, which will be passed on to the user in their task history.

  • Updates: Rarely, we are able to update duplicate contacts with data from the zap. WARNING: Updating can often mean over-writing in this case, so be aware if there's information in the action app you might potentially lose.

  • Stop/Ignore: Rarely, the zap will attempt to add a duplicate, but the action app will recognize the duplicate and take no action.


If you are having trouble with a Zap, this is the place to start. Even if you end up contacting Zapier support it is extremely important to provide context with regards to this debugging documentation so Zapier support can help you quickly without needing lots of back-and-forth emails.

This guide will walk you through identifying common problems that might have gone wrong setting up or running your Zap.

Have you been able to finish your Zap and enable it? No Yes


Check if your Accounts are connected and working in the trigger and action steps . Read more.


Are any required options in your trigger step filled in? Read more.


Are you using Placeholders in the action template? Read more.


Having trouble loading sample data? Read more

Missing Data Modal

Trouble sending data to a Service? Check out our service-specific documentation.


You have turned your Zap On but something is wrong with it. If you can't Trigger your Zap, even though it is On, try these steps:

  • Go into your Service (like Evernote, Salesforce, etc.) and create a new item

  • Go to your Zapier Dashboard and refresh the page

  • Wait about 60 seconds to make sure the Service API reflects the new item

  • Click "Run" next the Zap in question.


  • If you see "Found 0 items", continue

Zero Items

Did you expect Zapier to sync old items already inside your Service? Zapier only syncs new items going forward. Learn more.

  • Click "Edit" and go to the "Test this step" option of your final action.

Step 6

  • Click on "Create and Continue" to test the step, or if you've already tested this zap. click on "Re-test (app) to get another (record)".


  • If you've already tested this zap, you'll need to go to the "Test this step" option of the trigger app, then click on "Re-test (app) to get another (record)" before testing the action step.


  • Re-testing should pull up the most recent record you created in your trigger app.

  • If you are able to find it, then you probably just need to be a little more patient waiting for your Zap to run in the background (or try copying your Zap from the dashboard and deleting the old one to recreate it if you suspect there are problems).

  • If you don't find it, then there might be a mis-understanding about what data Zapier can actually see for a specific trigger or set of Filters, check out service-specific documentation for more nuances.

  • If you're still having trouble, contact us and let us know which steps you followed and what behavior you saw. This will help Zapier support track down the problem quickly.

Task History#

Your Task History is where you can see all the activity from your Zaps. It's a log of everything that Zapier tried to automate on your behalf. You can see all the data we get in and send out, so it's a great place to troubleshoot if something's not working as you'd expect.

How do I find my Task History?#

You can find your Task History from the tabs at the top of your account like this:

Task History

Or by directly going to this page: You can view your Task History on your account here:

How do I filter my Task History?#

To help you track down a specific Task a little faster, you have a few ways to filter your task history results.

Filter bar

You can filter by results for just one specific Zap, the error status of the task that happened and also you can specify a date range in which the task will have run.

Specify a date range

If you are looking for something more specific than that, there is also a search you can use to filter by a keyword or phrase that will have been the data for that task.

Search Tasks

You can also combine more than one (or all) of those filters to narrow down your results even further.

What does the "status" of a Task in my Task History mean?#

Each Task may have one of 5 statuses:

  • Success: This Task was completed successfully.
  • Filtered: This Task didn't pass the Filter condition.
  • Stopped: This Task ran into some error running, click it for more details. If a Zap hits too many errors in a row it will be automatically paused.
  • Waiting: This Task is waiting to complete. Zaps that have a Delay by Zapier step or are scheduled to Autoreplay will have this status.
  • Holding: This Task is being held. Please refer to the Holding Reasons section for more information.

Statuses have associated reasons to give you more information about that task.

Stopped reasons include:

  • Errored: This Task ran into some error running, click it for more details. If a Zap hits too many Stopped tasks due to Zap Issues in a row it will be automatically paused.
  • Halted: This Task was stopped on purpose by Zapier. Unlike Zap Issues, many halted Tasks will not automatically pause your Zap. For example, MailChimp rejects duplicate email subscribers to an email list. Instead of logging this as an error, Zapier will mark it halted.

Waiting reasons include:

  • Delayed: Used by the Delay by Zapier actions waiting to run.
  • Scheduled: Used by the Autoreplay feature for replaying later.

Why do my Tasks have a status of Holding?#

  • High Task Use: Too many (100+) of these Tasks were triggered at once. This "flood protection" prevents a significant number of tasks being performed by mistake. This helps keep your Task usage down and prevent tedious work correcting those unintended Tasks.
  • Reconnect {App Name}: The connection to one of the apps used in the Zap is broken. Reconnect the app from the Connected Accounts page first before replaying these Tasks.
  • Upgrade Needed: The account has passed its plan limit for Tasks or Zaps, or using a Premium App no longer supported by the plan. To replay these Tasks, an upgrade will be required first.
  • Payment Issue: The payment information on the account has expired. To replay these Tasks, updating this payment information will be required first.

Once the held reason has been resolved, these Tasks may be replayed.

How long do you store my Task History and what information is stored?#

In your Task History you can filter to a specific Zap's activity using the dropdown at the top. You can also filter on specific statuses and reasons.

Your Task History will not show activity if your Zap checks for new data and does not find any. If it gets an error while checking for data, that will be reflected by a Stopped status and appropriate reason.

Your Task History will store a maximum of three months rolling data of your tasks (but we can only guarantee a month rolling) or the last 10,000 tasks -- whichever comes first. If you need to keep longer term records of your task usage, we recommend regularly exporting your task history as a back up.

How do I export or download my Task History?#

You have the option of exporting your Task History to CSV by selecting tasks and using the Download action from the action dropdown.

How do I replay a Task that was not successful or had an error?#

There are a two ways you can replay tasks: manually and autoreplay.

Autoreplay: available to Professional Plan or higher users, automatically retry Zaps which encounter an error. Details here.

Manual task replay: available to all paid users, replay or fix non-successful Tasks that ran.

You can replay tasks individually or in bulk (up to 5,000) by selecting one or multiple tasks and clicking the Replay action button. You can monitor the status of your replay job in the notifications dropdown. Once it completes, you will see a summary of the results.

Replaying a Zap only executes the failed tasks, not successful tasks. So for example, say you have a Zap that triggers when a new contact is added in your CRM, sends an email, then updates a Google Sheets spreadsheet. Let's say the email gets sent successfully the first time the Zap runs. Replaying the Zap will only attempt to add the contact to your spreadsheet, NOT to send the email again.

Sometimes we are unable to replay your selected tasks and you will see the reason listed in the notification box. Reasons we may not be able to replay a task include:

  • The zap is paused: turn on your zap to replay these tasks.
  • The zap has been deleted: tasks associated with a deleted zap will not replay.
  • The zap has changed too much: tasks associated with a zap that has changed significantly will not replay.
  • The task is too old: tasks that are older than 2 months will not replay.
  • The task was already completed successfully: tasks that have already played successfully will not replay.
  • The task is already scheduled to replay: tasks that are already schedule to replay are will not replay.

In certain cases replay will be unavailable. This can occur due to an internal issue or when a replay job is already in progress. In these cases, wait for the job to finish or the internal issue to resolve and try again.

How do I delete Tasks from my Task History?#

You may choose to delete your Tasks from Task History. This will remove them from your Task History but it will not remove them from your Task count. Visit this page to learn more about what counts as a Task.

Select one or more Tasks, then click the Delete button to delete them from Task History.

What do the "Data In" and "Data Out" tabs mean?#

In your Task History you'll notice that each step for a task has a "Data In" and "Data Out" tab.

Trigger data#

On your Trigger, "Data In" is data we Sent initially to your Trigger Zap. In the example below, here's the info we Sent to an RSS feed with the "Data In" tab:

On the "Data Out" tab, you'll then see all the data that we received on to us from your trigger app. In the example below, here's the info we received from an RSS feed via the "Data Out" tab:

Action data#

On Action and Search Action steps, "Data In" is the data we sent to your Action app. In the example below, you can see the data we sent to Twitter:

On the "Data Out" tab, you'll see any data we received back from your app. Some apps return a copy of what was added, but not all apps or actions will have any data to send back to us here. So it's not unusal for "Data Out" on an action to be blank. In the Twitter example from before, you cannot select "Data Out" since Twitter has nothing to return to us.

Why is my Action step missing data in my Task History?#

If you ever notice that some of your data in your Task History results is in curly brackets like this {{ - it means that we didn't get anything sent on for that field from your trigger.

In this example here, it looks like we're missing a "Message Text" field:

The best thing to do is check out the "Data Out" tab on your Trigger step, that will show you all the data we got sent on from the trigger Zap. In this example, it looks like there was no "message text" sent on from Slack. So we'll likely want to re-map the Zap template and choose the "text" field instead.

To do that, first re-test your Trigger step in your Zap, that will ensure your Zap has an up to date sample in. Then delete that field on your Zap template step and re-add it in from the insert fields drop down.

Firewalls and IP Restrictions#

If you are using MySQL, PostgreSQL, or SQL Server, these three specific integrations will use a static IP. For more information, visit each of their help pages: MySQL, PostgreSQL, SQL Server

In all other cases, Zapier does not have one static range of IP addresses. Instead, we use ​Amazon (AWS)'s US-EAST-1 region, spinning up instances as needed. This means there could be millions of IPs to whitelist, which oftentimes becomes impractical.

You can find Amazon's list of current ranges (subject to change) here. We might be connecting from any of the us-east-1 ranges listed on this page:

How do these IPs translate into ranges?#

An IP like this: is listed in "CIDR" notation, which is shorthand for a block of IPs. If your firewall or filter does not support CIDR notation, you can convert this into an actual range of IPs by using an online CIDR calculator.

To calculate the range, type your IP block in:

The resulting calculation will give you a Start IP and an End IP:

In most cases, whitelisting all of us-east-1 is not going to be the right solution. You'll need to open your instance to the wider internet.