As a Jira user I’ve been using Zapier’s Webhook polls for years to trigger each time a subset of Jira tickets is updated, then perform a variety of actions. Recently we migrated to another Jira workspace so the URL and Webhook authentication info changed, but the rest of the zap was left alone.
Over the last few days I’ve been having an issue where the Webhooks are now triggering once for each ticket and then never again, so each ticket only gets one update detected even if several more are made throughout the day. I’ve tested this extensively and boiled it down to a simplified zap that consistently reproduces the issue, pictured here:
The Jira API being polled is really simple, when it picks up on an update to this ticket it returns some data in the following format:
I’ve tested this as extensively as I could to try and describe it better here: my updates to the ticket are just adding a space to the ticket’s title and saving. This should trigger the webhook every time, but instead it works the first time and then stops no matter how long I wait before making another update. It makes me think that the Webhook is either not refreshing its results, or it’s deduping all the subsequent updates despite the “updated” timestamp from the API response being completely different each time.
The only workaround I’ve found is to turn the zap off and on again, or clone it and turn off the original. Both of these methods have consistently gotten the ticket to be detected again, but then the Webhook goes right back to not detecting any further updates I make.
Is there something I could be doing wrong here? Or at the very least is there a way for me to see what the Webhook is polling in the background to know whether or not the deduping is the problem? We use these update-detector Webhooks for thousands of tickets so any help would be greatly appreciated.