It happens when the orchestrator did not get the signal for the end of the execution
We’re looking at your workflows and the executions
I’ll revert the logic back to v2 builder and see if that provides an output
It seems that the v3 split is not giving me much to work with here
p_BjCadpp had a constant ~100 executions in 09/09 to 09/11
The number of executions jumped in 09/12 to 1025, then were in between 800 to 900 on 09/13 to 09/15
Please DM me any links
They’re not accessible by other users
I intentionally used the workflow ID instead of the workflow name.
No issue, just for privacy purposes of identifying my account (which is in the URL) - it would be good to DM links instead of sending them in a public Slack workspace
p_gYC8j5M started executing in 09/12:
• 622 executions in 09/12
• 721 executions in 09/13
• 1007 executions in 09/14
• 1104 executions in 09/15
Thanks, I’ll have another look into all of this with my developers today