Yes and it’s still here from our end.
New info I understood since my last post:
- the problem isn’t there for all workflows
- the executions history for these errors doesn’t take new workflow edits into account: it displays the workflow state as it was when the error started
- it doesn’t seem to impact new workflows containing webhook created since
=> So it seems we can fix it by recreating workflows that are impacted. But they are quite a few in my case and it doesn’t mean it won’t happen again, understanding the reason will definitely help ![]()