Hi @KingOfKings
Can you post screenshots showing how the Zap Filter step conditions are not working in live Zap Runs (DATA IN/OUT)?
https://zapier.com/app/history/
@KingOfKings
Here’s why…
In Zap step 3, when you create an Event, it gets a new unique ID.
So in Zap step 3, the Event Subject has the Event ID from Zap step 1, which is different from the Event ID created in Zap step 3.
That means the Filter conditions in Zap step 2, will never be met, because the the Subject has the a different Event ID that being compared when the Zap triggers to run.
Instead, try including a common value to use to filter to indicate the GCal Event was created from another Calendar.
e.g. Subject = bSUBJECT] - XXX
Where XXX would be a static value. (Change XXX to whatever you want.)
Then you can Filter by the XXX in the Filter step condition to prevent the looping.
@KingOfKings
Here’s why…
In Zap step 3, when you create an Event, it gets a new unique ID.
So in Zap step 3, the Event Subject has the Event ID from Zap step 1, which is different from the Event ID created in Zap step 3.
That means the Filter conditions in Zap step 2, will never be met, because the the Subject has the a different Event ID that being compared when the Zap triggers to run.
Instead, try including a common value to use to filter to indicate the GCal Event was created from another Calendar.
e.g. Subject = bSUBJECT] - XXX
Where XXX would be a static value. (Change XXX to whatever you want.)
Then you can Filter by the XXX in the Filter step condition to prevent the looping.
Thank you, a static variable rather than a dynamic indeed fixed it.
Wow! Thank you for confirming that Troy’s resolution got the Zap running. This will significantly help our Community members to have as a reference for the same issue.