Short answer
Why Is My Airtable View Trigger Missing Records?
An Airtable view trigger misses records when they were already in the view before activation, briefly enter and leave between checks, or the integration watches a different base or view. Verify the connected base and view, create a new record that crosses into the view after activation, and use a durable queued status rather than a volatile formula condition.
Common causes
- Existing records do not count as newly entering the view.
- A formula or lookup makes the record enter and leave too quickly.
- The view has hidden filter groups or changed conditions.
- The connection points to a copied base, table, or similarly named view.
Diagnostic steps
- Confirm base, table, view, credentials, and trigger activation time.
- Read every filter group and test which exact field transition creates membership.
- Create a brand-new record outside the view, then change it so it enters once.
- Use a stable Ready status and a separate Processed status for production queues.
Example
A record was already visible when the Zap was turned on, so no new-entry event occurs. Move a test record out, then make a fresh qualifying transition.
Caveats
Views are presentation and filtering layers, not durable queues. Formula-driven membership can be too transient for reliable processing.