Zap is triggering but missed some runs
- Tables
-
Product updates
Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
- Zaps
- Your Zapier account
- Interfaces
- Canvas
- Chatbots
- Getting started
- Agents
- MCP
- Built-in tools
- Lead Router
- Apps
Table of Contents
Your Zap is running, but you notice that it missed some data from the trigger app that should have triggered your Zap.
Cause
There are a few different causes for this:
Data pagination in polling triggers
If your Zap uses a polling trigger, and the app creates more items than the trigger expects, the Zap might miss some information. This happens because the app uses data pagination to limit the amount of data sent to Zapier.
The maximum number of records that can be retrieved per poll varies depending on the app and the specific trigger used.

For example, you have an app in your Zap trigger that can only retrieve 100 of the latest records every time it checks for new information (a process called a poll). If you created 124 records in your app, that polling trigger will miss off the earlier 24 records, as it's beyond the app's limit.
Trigger conditions
Your trigger condition may be too restrictive, preventing some expected records from meeting the criteria and triggering your Zap.
The app’s API might not recognize the record you created
In certain situations, an app may not recognize a record if it does not meet the API’s specific criteria. For example:
- Records created manually through the app’s interface might lack the identifiers or metadata required by the API to trigger the Zap.
- The API may only recognize or interact with data that was originally created or updated through the API itself.
How to fix it
- Go to your Zap history.
- In the
- If a Zap run is found, review the Zap run further. Your trigger may be working, but other steps of your Zap cause your workflow not to run as expected.
- If no Zap run is found, continue onto the next steps.
Search your Zap run field, enter data associated with your missing record, like an email address or an ID. This will help to confirm if Zapier was able to trigger on that record.
Polling triggers
Check if your trigger is a polling trigger:
- Go to the Zap editor and review your trigger step.
- If it has a clock icon with a time stated, this means it’s a polling trigger and this solution applies to your Zap.
- If it has a lightning bolt icon , this means it’s an instant trigger and this solution does not apply to your Zap. Continue onto the next steps.


If you're using polling triggers, there’s a few things you can do:
- Depending on your Zapier plan, you can adjust your Zap polling frequency. This allows Zapier to check for new information more often, potentially reducing the pool of available records and allowing the Zap to retrieve them all. This will not bypass an app’s pagination limit.
- Recover any missing information by doing a one-time transfer.
Trigger conditions
Check your triggers conditions (if applicable):
- Go to the Zap editor and review your trigger step.
- If your trigger has a Configure tab, review its current settings. Clear or adjust any fields that may be preventing the Zap from finding your record.
App’s API restriction
To check if an app has an API restriction:
- Search the app’s help center or API documentation for restrictions or limitations.
- Contact the app support team directly. Most Zapier apps are built by the business themselves and they can confirm any known limitations with their Zapier app.
Still need help?
If this article did not fix the issue, Zapier has a few other options to get you the help you need:
- Contact Zapier Support. Our Support team can investigate your account to find solutions.
- Ask in the Zapier Community. Get advice from experienced Zapier users in the Zapier Community.
- Learn more about getting help. Read our guide on how to get help and support with Zapier to find the best resources for your specific problem.