You can certainly try, but we no longer support v1 workflows to patch the underlying system for them. I highly reccomend using v2 workflows for new workflows.
The other limit to consider is the connected account limit, that also could be the cause.
ugh
nvm
Were you able to figure it out?
no
but neither did you
I understand you’re frustrated, but please consider there are humans on the other side of the screen.
There are 10 connected accounts available to use in workflows on the Basic plan.
Sorry for my rage.
Thanks for your support.
Have a good day
Of course, happy to help. It sounds like you found the issue, but if you need anything else please let me know. Thanks again for your patience.
I will just copy working workflow and redeploy it
Best of luck, hope that addresses the issue.
It is a workaround of the bug. I faced that a year ago
Just a friendly feedback: please create some toolkit so you could investigate the problem yourself but not guess with a user various potential problems.
If user hits limit of workflows/connected accounts and anything else, please show him the error in the UI so you could be sure that stuck deployment without any messages is not the problem and could start troubleshooting the actual problem.
Thanks for the feedback, we always appreciate it.
In v2 workflows there is feedback to show when a limit has been reached, so you’re able to diagnose that issue yourself. We’re discussing an update to this feedback to show exactly which type of limit prevents a deploy, but again this feedback would not be available in v1 workflows.
But v1 workflows do not have this banner because development has ceased on that system since early last year, also admin tooling around v1 workflows has stopped as well so we can continue to focus on iterating the newest version of the product.