As there is no updates coming out, I created a new post as this is a separate issue. Conditional Paths are not working when the variant being searched is being sent from Airtable.
As there is no updates coming out, I created a new post as this is a separate issue. Conditional Paths are not working when the variant being searched is being sent from Airtable.
Be aware there is a current incident related to Filters, which Paths use: https://status.zapier.com/#incidents-list
By way of update on my end - I have just had two zaps go through. Which i the first time I have seen one succeed in the last 20 hours - so that is a positive. Well I am taking it as a positive step forward!
They were both using conditional paths also.
Unfortunately, it looks to be related to the same known issue with Airtable Zap trigger data, and we’re at the mercy or awaiting a fix.
A possible workaround would be to reconfigure the Zaps, as such…
Make the Zap trigger a Webhook.
Use Airtable Automations to send data to a Zap Webhook per the article below.
Make Step 2 of the Zap an Airtable Find Record action.
Then map the data from Step 2 to subsequent Zap action steps.
NOTE: I suggest cloning the Zaps so you have backups for when the issue is resolved.
This happens across all zaps that use conditional paths, zaps that have been working fine for the last 12+ months.
Sure, here you go - using the same data as the test data to what actually happened with that data when the zap ran:
The test shows as working, now that exact same data when the zap ran:
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.