Zapier can help make Airtable do awesome things, but I’m finding it intensely frustrating when developing and refining a new Zap that a backlog of Airtable records can develop that should be candidates for processing by the Zap, but wont be processed at all because they are no longer ‘new’ records in the view.
Even if I create a dummy view using same filters, and assign the Zap to process the records in that view it still wont work because the records are already in that dummy view when the zap is assigned. Other problems occur if I assign the zap to the dummy view then update the filters to populate it because there is no initial candidate record to test and validate the Zap.
What is the best practice way to manage this? Its driving me mad!