This topic was automatically generated from Slack. You can find the original thread here.
It’s already the second time a delay is stuck and not sure why but it’s very disappointing.
Here’s the Workflow and I turned on the support access.
Can you guys take a look?
Hi Doron, the top execution is paused because you have a delay step — if you scroll down to the step, you’ll see the delay step executed and you’re currently within the delay period
re: the other execution at the bottom, I’m not sure what the issue is — can you try replaying that event if you need to run that execution specifically?
Hi, the top one has 10 hours delay but it’s gone already and it still stuck.
Second at the bottom didn’t even continue
Can’t run it manually because the time is gone
thanks, I’ll look into the top execution
Ok thanks let me know it’s super important for me
Hi, any update?
Hi Doron, yes, I’ll explain exactly what happened. We’re still discussing how to address the behavior. While the execution was paused, it looks like you shipped a change to rename the delay step. When we tried to resume the workflow, we key on that step name. Since we failed to find the step with the original name (pre-suspend), we failed to continue the workflow. We’re working to resolve the core issue, but it looks like today’s execution ran OK, so I’m hoping this will not be an issue for you in the future.
Hi ,
It should run tomorrow a full workflow so I’ll check. thanks.
Another thing that just happened is that I have a one Cron and for some reason it runs twice today instead of one, you can see that all others triggered one, can you please check why?
You have access
