I’ve set up a Zapier workflow that is triggered whenever an Asset Label is updated (Needs review, approved, etc.). It works most of the time, but there are some times that it does not work.
I have to then go in again, change it to “no status” and then back to the correct status.
When I do that, the zap is triggered twice (like if it was stuck or something).
How can I fix this? This workflow is used up to 50 times a day so it’s something I rely on a lot. Doing it manually is extremely time consuming.
This is something I raised with engineering when I first saw your post but forgot to respond. It turns out there was actually a somewhat recent change to this behavior which should have actually improved how webhooks are triggered from status label changes.
There is some additional engineering work going on right now to improve our webhooks subsystem further to reduce latency spikes in worst-case scenarios that should further reduce the chance of this happening.
We were not able to replicate this exact issue ourselves, so please let us know if you continue to experience this so we can debug further!