Hello!
I have a fairly complex zap logic and in general my zap is working well. The flow of the zap logic is such that after a number of successful steps, I place a filter step, and only those events that filter through successfully get executed further. In my scenario, this filter is applied for 95% cases, with only 5% cases passing through.
For example, I receive a list from the source system, and my filter checks if it’s an empty list. If not, then there is a loop (Loop by Zapier) to iterate through each list element, and the destination system is updated with the element value. If the list is empty, of course, then the filter kicks in and the Loop step onwards are avoided. Note, there are a few successful steps executed before this, including one update into the destination system.
My annoyance is that in my zap history or status, this zap is showing “Filtered” -- whereas I would prefer for it to show “Success”. After all the logic did execute successfully. Here’s why this matters: in a high volume environment, when an admin is trying to track the status of the zaps, these reports are spooking the analytics and leading the team to spend cycles investigating successful events.
I may be wrong, but for some other zaps that have a similar filter, which kicks in less than 5% times, the zaps are showing success. In these cases, the filter is preceded by a PATH step within a zap. Could that be affecting the status reporting?
I am aware that this may not be easy to “tweak” -- but I would like to. For now, I do wish to report that this is a wrong and misleading success report by zap that is not having an actual failure in data integration, but is causing confusion when it comes to administration, and I hope Zapier understands this.
I would love to hear back from Zapier support on their take on this.
