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: https://zapier.com/app/history

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.