No it's in the sense of performance, previously my workflows were taking 8 to 15 minutes to complete
No it's in the sense of performance, previously my workflows were taking 8 to 15 minutes to complete now they are taking almost 40 minutes +
Jmaybe a hour
Sthey are taking that time from running to a completed state or from a queued state to a complete one? anyway can we have your account id so we can look at it?
JFor running to completed state. sent you I'd in DM
Jnot able to DM you
SHey guys,
I am getting an error when using this new Workflow API sendEvent in the production environment. Local works as expected.
Error message:
I am getting an error when using this new Workflow API sendEvent in the production environment. Local works as expected.
Error message:
AHey and congrats for GA 
!
Is it possible to have an in-progress state that could be queried? In the case of an onboarding workflow, while we wait on a specific outside event, we can fetch the status of the workflow and some arbitrary data. Maybe similar to Temporal Query feature?
! Is it possible to have an in-progress state that could be queried? In the case of an onboarding workflow, while we wait on a specific outside event, we can fetch the status of the workflow and some arbitrary data. Maybe similar to Temporal Query feature?
Jupdate your project wrangler version
SI think it's already at its peak
Jit may be a global wrangler, check inside package.json what is the wrangler version
SSame - 4.8.0
Jdid you generate types ? npm run cf-typegen
SYes
MIs
workflowWorkflowInstance- ? Can you call
successfully?await workflow.status()
Jhi guys - is there a way to repeat the workflow multiple times? for example, when i go through step 1 - 5, and if some condition isnt met, start again from step 1. sort of like a recursive function
GIs there plans to have a template like other workers as an example?
GI see the example but I find working templates are a much better way to get started
SYep - It is a
Logging -
WorkflowInstanceawait workflow.status()sendEventTypeError: a.sendEvent is not a functionLogging -
MCreate a new Workflow instance from inside the current Workflow
M@Diogo Ferreira @Seekerdasbatatas since I’m travelling / in transit
MHave you seen:
we’ll be adding this to wrangler soon, but it’s the same template
we’ll be adding this to wrangler soon, but it’s the same template
AMaybe storing something in KV as part of a step with the key being the workflow id, and having the 
fetch
CI have a platform which is something like Zapier. My user want to schedule their own CRONs. Like run this action every 5 minutes. Is this something I can do with workflows?
MCan you describe a little more about what you're trying to do? Workflows are great for multi-step / async tasks, but aren't themselves a "task scheduler" - you can use Durable Object Alarms, the Agents SDK (and the scheduling API), or even Cron Triggers to schedule tasks - incl. Workflows.
Gno I did not, I was under the impression templates were in the dashboard
CPretty much say my user has a workflow like:
Search for new concerts in Rome and email me if tickets are less than 50$- run it
every 6 hours
- run it
MI'd consider using an Agent - e.g. an Agent for each user + the Agent schedules a ticket-search Workflow that runs the search + validates prices + reports back
MThis isn't the same, but it's similar: each repo is associated with an Agent -> the Agent kicks a Workflow for each PR.
In your case, it's an Agent per user, and the Workflow is for a ticket-search (instead of a PR/code review):
In your case, it's an Agent per user, and the Workflow is for a ticket-search (instead of a PR/code review):
CYeah I'm looking at the agents api
Cthanks
CHey guys, Should I move all of my complex tasks in workers into workflows? so far it seems like it doesn’t have that much disadvantages aside from being a little bit complicated.
Gworkflows seem a lot more streamlined an maintainable then doing the tasks independently, especially if they involve multiple workers or services.
theres also some things unique like the r2 trigger that could be really usefull on its own
theres also some things unique like the r2 trigger that could be really usefull on its own
GI'm going to try and move one of my pipeline systems over and see how it goes, it looks promising
CYeah, that’s really attempting
Gthats why I am glad theres a template as a starting point , give me something to start with and migrate over the pieces
SHi, I've added a reproduction repo in this issue - https://github.com/cloudflare/workers-sdk/issues/8850
GitHub
Which Cloudflare product(s) does this pertain to? Other What versions & operating system are you using? wrangler v4.9.0 Please provide a link to a minimal reproduction https://github.com/Suman0...
HHello, is there any way to start multiple different workflows in batch ( using only one request ) I know we can start multiple invocation of the same workflow using the createBatch but IDK about different ones
Gas in a workflow invoking another workflow?
Ha worker invoking multiple workflows at the same time
GI haven't dug into it yet but you could just have it invoke the triggers for each right?
MCall
.create
DHI! Sorry for the inconvenience. Our edge runtime update that brings support for
instance.sendEventIs workflows now out of beta? OK to use in production?
JThe Cloudflare Blog
Workflows — a durable execution engine built directly on top of Workers — is now Generally Available. We’ve landed new human-in-the-loop capabilities, more scale, and more metrics: just what you need for a production-ready service.
MI'm running into a somewhat frustrating auth error when trying to trigger or list workflows via the
cloudflareSomewhat related to the above, is logging from workflows captured in the worker logs?
I have this in
I have this in
wrangler.jsoncHey, I think there might be a bug with Cloudflare Workers.
Whenever I update any binding (like a KV namespace) from the dashboard and deploy the changes, the binding for the Workflow gets removed automatically. This seems unintended and could cause issues during deployment.
Whenever I update any binding (like a KV namespace) from the dashboard and deploy the changes, the binding for the Workflow gets removed automatically. This seems unintended and could cause issues during deployment.
Jthis is happening after the GA of workflow
MIf you are mixing the dashboard + wrangler you can run into conditions like this - strongly recommend using one model to deploy. cc @Sid Chatterjee if we can make sure Workflows bindings stick here.
Jbut what if I am out of my work station and I need to urgently update some Vars, secrets etc. first thought will be to use dashboard from mobile.