Workflow instances never being tiggered
Hello guys
Im facing a problem where my workflow instances get queued but never starts
This started may 15th, on that time, I noticed that when we manually paused some wf queued instance, all instances above it were triggered
then I publised a worker that basically start, pause, and finish a wf instance so my routines could be triggered
That worked until today (June 18th); this morning, none of my instances are being triggered, even with that start/pause “quick fix”
There are some crucial routines to our company, i'm even thinking about trying to migrate those routines to other account or even service
We're using a lot of cloudflare services and investing around 4.5k usd monthly
Could anyone help me with that matter?
11 Replies
@gamarra2042 @Cristian Lipinski can you both run the /link command so that we can look into your accounts? If/Once you do tag me and I will have a look.
Thanks in advance
sure! Just did it, we're talking about the same cf account, I'll ask gamarra to do the same anyway
done
@avenceslau anything more we can do? its a urgent matter for us...
Looking into it
Last month, we created a workflow called seed-kv-1m to try out some things, but due to a mistake, we ended up generating too many instances. Since then, our account stopped automatically starting instances. So we had to create a workflow that would pause and start instances, which worked for us for 30 days. Now, no instance is running at all
We are unblocking you right now, we are shipping a fix right now.
Regarding your account not triggering we will look into it that tomorrow.
@gamarra2042 @Cristian Lipinski I think its solved could you check
it seens its triggering normally now, thank you so much @avenceslau !
Friday we will have a another look at your account, I might need more information, I will get back to you if I need
sure thing, we'll keep an eye at this topic then
Thanks, I will keep you posted
Regarding this how did you stop that workflow, what were the steps you took? cc @Cristian Lipinski
after the mistake that endup calling instances recursively, we tried to delete the enterely workflow, because we werent even able to list the queue at the moment
then after that we created another workflow with the same name, trying to "clear" any qeued itens
after that our account wasnt the same until you helped us
and as feedback our workflows are working completely fine since your help