Hey there ? Is there possible to add workflows inside an existing worker ?
Hey there ? Is there possible to add workflows inside an existing worker ?
AYes, you just need to export the class that implements your workflow and set the appropriate bindings in wrangler.toml as per the docs
F@Ashley thanks, the idea is that some functionalities of the worker to be executed as workflow steps.
and also the existing worker is in js, so far there is only documentation in .ts
and also the existing worker is in js, so far there is only documentation in .ts
DFor how long after a workflow is finished,
WORKFLOW.get(id) will return the finished instance? Also, does .restart() work for finished workflows too?
MI am on the Workers paid plan.
For at least 3 - 4 days I see that the workflows are flowing... not as expected.
They build up a massive queue (which seems to grow bigger day by day) and have long inactivity periods (as visible on the screen—before that, there was no activity for 1h+). Meanwhile, usually I've not seen more than 28 instances running, in rare cases they hit at one moment higher, but havent seen near 100.
The workflow itself contains just one simple request (to Meta conversion API), so there is nothing resource-demanding (because I'm testing if and how to scale the workflow usage).
At the error logs I see that the requests might fail due to "Durable Object restarting," because of some code updates. Thats cool, but I'm just waiting when this queue will be "errored" when the wrong timing hits.
So my concerns and question is - are there some other limits that must be taken in mind when building the Workflows? Or is this some issue related to my account or what?
I understand that it's low possibility to get an answer here, but I still hope on that. :))
Thank you .
For at least 3 - 4 days I see that the workflows are flowing... not as expected.
They build up a massive queue (which seems to grow bigger day by day) and have long inactivity periods (as visible on the screen—before that, there was no activity for 1h+). Meanwhile, usually I've not seen more than 28 instances running, in rare cases they hit at one moment higher, but havent seen near 100.
The workflow itself contains just one simple request (to Meta conversion API), so there is nothing resource-demanding (because I'm testing if and how to scale the workflow usage).
At the error logs I see that the requests might fail due to "Durable Object restarting," because of some code updates. Thats cool, but I'm just waiting when this queue will be "errored" when the wrong timing hits.
So my concerns and question is - are there some other limits that must be taken in mind when building the Workflows? Or is this some issue related to my account or what?
I understand that it's low possibility to get an answer here, but I still hope on that. :))
Thank you .
MAddition to previous post - here is the situation on another Flow - queue just getting bigger, but nothing is processed. It feels like that only one workflow connected to the worker is running. Did I miss this limit somewhere if its true?
SAre there any other workflows in your account? Note that the concurrency limit is account wide
MNo. These are two working workflows, which basically do the same thing.
By looking into possible solutions I divided the requests in half.
That helped a bit, as the active one started to process something and now the queue is slowly decreasing, but the other one - does not do anything, and now is up to 2k in the queue (both waiting queue sums are the same as before and keeps increasing).
For wider context - they are receiving the requests from the Zaraz custom-managed component. But I don't know if it has anything to do with this unless that affects some other underlying processes.
By looking into possible solutions I divided the requests in half.
That helped a bit, as the active one started to process something and now the queue is slowly decreasing, but the other one - does not do anything, and now is up to 2k in the queue (both waiting queue sums are the same as before and keeps increasing).
For wider context - they are receiving the requests from the Zaraz custom-managed component. But I don't know if it has anything to do with this unless that affects some other underlying processes.
SHuh weird, thanks for letting us know - can you send your account id for us to investigate?
MYes. As already sent before, here it is.
My account ID: 5e3dea7b807381cba36b9292bde14920
My account ID: 5e3dea7b807381cba36b9292bde14920
SThanks, I'll look into it tomorrow morning
M
JDo Cloudflare workers bindings/apis work inside Workflows ie the AI binding?
JAwesome thx 
MWhat I can add now after looking at the tendency, it is somehow related to the incoming requests to the workflow. Now, after the peak hours are over, the processing tempo has increased proportionally to the decrease in new requests.
I hope this somehow helps investigate further and find a solution.
I hope this somehow helps investigate further and find a solution.
DBumping this in case anyone knows
SOn limits, we advertise 3 days on free and 30 days on paid (although this is not enforced atm, but could change at any moment)(https://developers.cloudflare.com/workflows/reference/limits/)
.restart() is not implemented yetCloudflare Docs
Limits that apply to authoring, deploying, and running Workflows are detailed below.
DOk, thanks!
KHi folks, we're seeing that if you execute a sleep step, it takes a few minutes to change states from running to waiting, and that backs up the queue pretty significantly. Would someone be able to explain in more detail why this would happen under the hood and what we should expect?
MHi - I'm new to Workflows. I'm a little lost in the various ways of doing things and am trying to understand how Workflows differs from other approaches to task distribution. In what situations would Workflows be preferable instead of, say, worker service bindings, or queues? Both allow tasks to be distributed and run asynchronously. A really simple use-case example would be appreciated.
STo keep you posted, the bug has been identified and will be rolling out throughout next week probably
LIs there an easy way to debug workflows in vs code? In my workers project I can just use the
javascript debug terminal and it works fine. For some reason it doesn't w/ workflows - all of my breakpoints are "unbound"
LDisregard - i forgot that w/ workers I don't use the
javascript debug terminal I have to run wrangler devNext question I have is - how can I restart a failed workflow? I tried using
instance.restart, instance.terminate, etc. and it says Not implemented yet. Any tips on that?
SIt's an implementation detail for workflows - we need to allow some time for top level work, this time might get reduced before GA, but for beta we were more generous because of correctness (because it's JS, you can do some really weird stuff with control flow in a relatively easy way 
)
)SWe hopefully are 
a bunch of stuff next week that will make the queuing aspect better :soontm:
a bunch of stuff next week that will make the queuing aspect better :soontm:LI'm trying to use Browser Rendering in my workflow but debug the code because:
- I can't run browser rendering locally (need to use
)--remote - I can't run workflows using using
--remote
console.logBy the way, workflows do not trigger for me locallly (dev) when created by worker. Works in prod. wrangler 3.107.2
CAlso what sort of concurrency is likely to be allowed in future, are these things intended for use at scale?
DCan someone give me an intro to this… I’ll ask ChatGPT
Aguys how can I get access to env variable in workflow?
Aexport class myclass extends WorkflowEntrypoint<Env, Params> {
async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
}
}
AI found it as a comment in example code:
// Can access bindings on this.env
Ftwo questions:
1) Is there an architectural icon for cf workflows yet?
2) anybody know where can I get a library of icons that I could use to build diagrams like these:
1) Is there an architectural icon for cf workflows yet?
2) anybody know where can I get a library of icons that I could use to build diagrams like these:
IINot sure about 1.
FOh that site is pretty sick - thank you!
AIs there a way to limit concurrent workflows based on their id? For example if the id starts with 'type1' only one workflow can be running at the same time
MNot yet. Looking at controls here by Workflow - e.g. a
max_concurrent_instancesNext big step is 4,500 concurrent (very soon) and we want to get to 10k (at least) over the next few weeks/this quarter.
Making sure it all works + nothing bottlenecks.
Making sure it all works + nothing bottlenecks.
ANice but not yet implemented right?
Scorrect
JCan I know the limit of memory per workflow ?
For workers it's 128 MB shared per invocation right?
For workers it's 128 MB shared per invocation right?
Sit's the same 128MiB on Workflows too (and depending on scheduling, it maybe be shared with other instances)
JOk it means every step will get 128 MiB or a whole workerflow ?
Sthe whole workflow
JOk thanks, well this is somewhat concerning if there are some tasks which use memory too much.
That's why may be my workflow steps are throwing an error of cpu/memory limit after doing work of around 128 MiB ( nearly )
But on retry it's again working till 128 MiB
what's this behaviour?
That's why may be my workflow steps are throwing an error of cpu/memory limit after doing work of around 128 MiB ( nearly )
But on retry it's again working till 128 MiB
what's this behaviour?
DDocs say
step.sleepah I see, thanks
