Hello everyone,
I’m encountering an issue where the “Canceling Runs” feature does not seem to work as expected in the Automation when multiple webhooks are received in quick succession. Despite triggering “Canceling Runs,” the system continues to process all incoming requests without stopping or canceling any of them.
Has anyone else experienced this? Is there a workaround or a known fix for this behavior? Any insights would be greatly appreciated.
Thank you!
Tom
Hi @tom.goeckeritz,
have you also paused the automation? The problem is that “Canceling Runs” only cancels the existing runs. To prevent new runs from being triggered, you must also pause the automation.
Maybe it would make sense to add an option that does both at once.
Best regards
Leo
Thanks for the quick support Leo! It’s working now without pausing the automation! 
Leo, I think that’s a great failsafe to put in place. It would be more intuitive for those of us who are unfamiliar. I love the way that you and the team works through practical solutions with the community. It’s been awhile and I’m still not used to that yet.