No, and to be clear, Airtable has no such issue with regard to triggering actions for the first time in a view. That issue is caused by Zapier; not Airtable.
Zapier - like all glu-factory integrations suffer the consequences lacking intimate knowledge of the current record state in context with the record history. To overcome this, they craft business logic that is limited and often misinterpreted. By “limited”, I mean capable of tracking only if the event has previously fired on a specific record ID. This logic is insufficient to meet most requirements concerning process automation.
Airtable’s newest (and only) event triggering mechanism is based on the flow of records in and out of views. If a record flows into a view 3 times, the event handler will fire three times.
If this is the case, it seems that the gating constraint is a no-code solution, so we’re probably wasting our time trying to get you down this alternate but likely successful pathway.