This looks to me like Zapier is excluding these records because they’ve been run already, but I don’t have a way to access the runs anymore.

copied the zap, changed the view in Airtable to exclude the records in question, turned on the zap, ran the zap manually, changed the Airtable view to show the records in question, reran the zap manually, “We couldn’t find any new records”, that did not work.

I turned off the Zap, changed the view in Airtable to exclude the records in question, turned the zap back on, waited 5 min, ran the zap manually, changed the Airtable view to show the records in question, reran the zap manually, “We couldn’t find any new records”, that did not work.

With Zapier, you can do more than just connect your apps - you can automate entire processes from beginning to end Check out the following list of triggers and actions you can use with Notion, Airtable, and Looping by Zapier. I deleted the zap runs to try to get the items to run again, “We couldn’t find any new records”, that didn’t work. Do even more with Notion + Airtable + Looping by Zapier.Zapier didn’t repull the data from Airtable to see that I fixed it.

Optionally: triggers when any record (new or existing) is first. Set it up and, as soon as a new Airtable record is created in a view, a Facebook page post will be automatically generated. I tried rerunning the Zaps to no avail. This integration lets you keep your followers up to date, without requiring any added clicks.I’ve since gone back to fix the Airtable data. Some of my event date/times had extra characters (“ET” for eastern time) appended on the end. → In On24, a new event is created with details from Airtable → On24 event details are pulled back to Airtable.

Airtable record zapier