I’ve had an issue with many clients in the past where users making very minor changes to zaps and forget to turn them back on (sometimes they didn’t even make a change but clicked into a field to check something). Is there a way to protect this from happening?
Other systems I’ve used in the past have a concept of “versions” and you make a new “version” leaving the old one activated until you’re ready to turn on the new version.
With web hook zaps this can be really frustrating as I then need to go to the web team to get the data that was missed while it was off.