This has been an issue forever. I have posted about it many times and others have experienced the sa

This has been an issue forever. I have posted about it many times and others have experienced the same thing. I have never seen Cloudflare acknowledge it, though. Supposedly, if you JSON stringify the response, you won't see an error, but even Cloudflare doesn't do that in any of the examples. Bottom line, this is a bug in workflow, but it doesnb't seem like they will ever fix it.

Dddsgadget This has been an issue forever. I have posted about it many times and others hav...

Seekerdasbatatas•7/2/25, 9:01 AM

While the invocation might show the invocation as errored/canceled, it's not directly related if your workflow instance threw or not, it's a side-effect of how we guarantee durable execution internally. You should refer to the instance logs (in the Workflows tab, in dash),to see if an instance failed or not.

But this is something that we should definitely fix in our logging pipeline, so sorry about that :MeowHeartCloudflare: , we'll try to get it fixed :soontm:

SSeekerdasbatatas While the invocation might show the invocation as errored/canceled, it's not dir...

ac•7/2/25, 12:18 PM

Thank you! That'd be hugely helpful for us, especially since it makes it show on our dashboard that we have hundreds of thousands of "Errors" (most of which are actually just workflows). Makes it very hard to understand our system health.

Olriko•7/3/25, 11:36 AM

Hello, I have a 429 error when I want to trigger a workflow from the ui (and I don't spam your api)

POST https://dash.cloudflare.com/api/v4/accounts/e97e3fed722428f4d726062eae9aa766/workflows/workflow-orchestrator-staging/instances

POST https://dash.cloudflare.com/api/v4/accounts/e97e3fed722428f4d726062eae9aa766/workflows/workflow-orchestrator-staging/instances

Mm0c What confused me, I think they only start showing up on observability when they ...

unsync•7/3/25, 4:19 PM

We started on workflows and this puzzles me, if I have a long running workflow, I get close to zero observability of what happen inside my steps until the whole execution is done ?

martinhoest•7/3/25, 7:43 PM

I must be fooling about with Workflows and Observability - or is it normal that a failing step of a Workflow will not add meaningful logs to Observability?

The error here is thrown within step.dostep.do but it is nowhere to be found from the logs tab of the worker. I also cannot find anything on the Instance ID of the workflow invocation.

SSeekerdasbatatas While the invocation might show the invocation as errored/canceled, it's not dir...

ddsgadgetOP•7/4/25, 2:17 AM

Thank you! yeah, I understand the error has no impact on the actual workflow. But, it is really annoying to see the errors in the dashboard when there is no real workflow error.

Gabriel Francisco•7/4/25, 3:46 PM

is it possible to see the logs of a particular step? this seems basic but I can't find a specific filter for that

Gabriel Francisco•7/4/25, 4:37 PM

my workflows are going to some weird "Waiting" state, even without sleeps, I would like to see what is happening but can't find any logs

martinhoest•7/5/25, 6:45 AM

What's the expected output in logs if one Workflow triggers another Workflow, but the instance ID of the latter already exists?

Will I need to loop through all created instances from await this.env.WF_FILING_INGEST.createBatch(batchParams);await this.env.WF_FILING_INGEST.createBatch(batchParams); and call their status()status() function?

Or it might be better to check for existing instance before creating new?

Bryan Chen•7/7/25, 9:52 PM

what exactly does this mean? the workflow status is completed, but the step is running and have no output?

BBryan Chen what exactly does this mean? the workflow status is completed, but the step is r...

johtso•7/9/25, 10:03 AM

Did you figure out what was going on?

Bryan Chen•7/9/25, 8:50 PM

no. I suspect the network request got hang but wasn't able to confirm it. and that still indicate some bug in the workflow

Advany•7/9/25, 9:51 PM

Is there already a way to use workflows using vitest?

https://github.com/cloudflare/workers-sdk/issues/7414

GitHub

🐛 BUG: Vitest does not work with workflows · Issue #7414 · clo...

Which Cloudflare product(s) does this pertain to? Miniflare, Other What version(s) of the tool(s) are you using? 0.5.32 [@cloudflare/vitest-pool-workers], 3.91.0 [wrangler] What version of Node are...

BBryan Chen what exactly does this mean? the workflow status is completed, but the step is r...

Jadugar_Jaggu•7/10/25, 3:58 AM

Maybe you haven't used await in your step. it's waiting for pending promise.

try awaiting every step "await step.do()"

JJadugar_Jaggu Maybe you haven't used await in your step. it's waiting for pending promise. tr...

Bryan Chen•7/10/25, 4:09 AM

I global searched it, every step are awaited. besides, if missing await can trigger this, it is a workflow bug

Bryan Chen•7/10/25, 4:13 AM

related question, the step timeout is 10mins, is it wall time or compute time?

AshuRajput02•7/10/25, 9:22 AM

hey everyone
so there is a site of mine say abc.com now i m thinking to apply zero trust policies in it . so basically i want ki user should be able to access the auth page only via warp client and not by directly hitting the url on website.
how to achieve this ?/

Jeffrey Konowitch•7/10/25, 11:22 PM

Clarifying Maximum Workflow instance creation rateMaximum Workflow instance creation rate Limit

The createBatch documentation says

call to createBatch is treated the same as a call to create (for a single instance) and allows you to work within the instance creation limit.

Does this imply that when using

createBatch

createBatch

, if you were to create 100 instances per batch (the maximum), that you could create 10,000 instances (100 per batch * 100 calls) per 10 seconds?

I understand there are other limits that might kick in (e.g. Maximum number of queued instances), but this example is meant to clarify the creation rate limit.

Worklows Limits Reference

Frank•7/11/25, 4:03 PM

trying to move one of our cache gen into workflow

list active users
fetch data
store into r2

my initial thought is having a workflow just to fetch users, then it kicks off another workflow to fetch and cache data based on user id
or better to just have a single workflow?

flof.fly•7/12/25, 9:54 AM

Can I invoke a Container from a Workflow?

flof.fly•7/12/25, 11:49 AM

Yes I can

Joentze•7/19/25, 3:54 AM

Seeking advice here, i want to create scheduled workflows. I want to create periodic tasks (i.e. daily at 9am, 1st day monthly), and one-time tasks (date xx at yy time). These workflows are dynamically added by the user via an api request to the worker. I’m using Hono to handle routing.

What should i use to achieve this?

JJoentze Seeking advice here, i want to create scheduled workflows. I want to create peri...

boop•7/19/25, 11:13 AM

Durable Object alarms are better suited for this

Yash Gupta•7/21/25, 9:29 AM

Has anyone tried to access steps/execution history for workflows from within their application?

It seems that the workers binding for workflows only gives present status and output, and while the API itself has steps history, it doesn't work for local development, making it hard to incorporate that as part of the solution.

Another option I've explored is manually intrumenting the step, waitForEvent and sleep methods, but it seems like redundant work (and possibly flaky)

alex (he/him)•7/22/25, 11:44 AM

I'm really having some issues with workflow creations

alex (he/him)•7/22/25, 11:44 AM

Already using

createBatch

createBatch

and try to create ~650 instances all at the same time

alex (he/him)•7/22/25, 11:45 AM

That would be 7 calls with

createBatch

createBatch

.. however I'm still seeing super long time until

createBatch

createBatch

resolves as well as a lot of too many requeststoo many requests errors.

alex (he/him)•7/22/25, 11:45 AM

This is super hard to debug and annoying too.. why does even

createBatch

createBatch

limits soo hard?

Bboop Durable Object alarms are better suited for this

Rahul gangotri•7/22/25, 1:09 PM

alarms will be expensive as it also charges on wall time, so if a task is taking longer to resolve or making call to external api is in place, then its going to cost for all that wait time.

ac•7/22/25, 2:08 PM

How likely is it that the "Maximum Workflow instance creation rate (100 per 10 seconds)" limit will be increased? This limit is pretty low for us

RRahul gangotri alarms will be expensive as it also charges on wall time, so if a task is taking...

boop•7/22/25, 2:20 PM

Make the DO call a workflow, just use the DO alarms as a scheduler

Aac How likely is it that the "Maximum Workflow instance creation rate (100 per 10 s...

alex (he/him)•7/22/25, 3:00 PM

This limit is pretty low for us

It's the same for us. We are already looking at alternatives to Cloudflare Workflows, since it doesn't work for high load use cases.

Aalex (he/him)> This limit is pretty low for us It's the same for us. We are already looking ...

Jeffrey Konowitch•7/22/25, 3:46 PM

I've asked about this three times and no response from Cloudflare. A bit concerning for anyone looking to build apps with even moderate throughput requirements.

workflows
Clarifying `Maximum Workflow instance creation rate` Limit
Is the workflow creation rate limit 100 per 10 seconds for createBatch?

hype•7/22/25, 4:07 PM

Same. Just running into this when trying to migrate

hype•7/22/25, 4:07 PM

and now looking again into alternatives.

Hhype and now looking again into alternatives.

alex (he/him)•7/22/25, 4:32 PM

There are not too many for our usage pattern. Also noone can really beat Cloudflare's pricing.

JJeffrey Konowitch I've asked about this three times and no response from Cloudflare. A bit concern...

alex (he/him)•7/22/25, 4:34 PM

I think what could work is use Cloudflare Queues and then consume settings to take batches of 100 each and use

createBatch

createBatch

, but then we would end up with

QUEUE A -> WORKFLOW A -> QUEUE B -> WORKFLOW B

QUEUE A -> WORKFLOW A -> QUEUE B -> WORKFLOW B

at which point I would argue, we can rely on Queues solely and not use Workflows at all.

alex (he/him)•7/22/25, 4:37 PM

So the fact that we also can't control concurrency on a per Workflow level means, that if you publish 600 Instances using

createBatch

createBatch

Workflow A

Workflow A

and every instance uses

create

create

to run

Workflow B

Workflow B

that will not work, because as soon as 101 or more of

Workflow A

Workflow A

run in parallel, we already hit the creation limit to create those "child" workflows

alex (he/him)•7/22/25, 4:38 PM

@Walshy

this would be Feedback you asked for on X

Walshy•7/22/25, 4:39 PM

cc: @Sid Chatterjee @Diogo Ferreira

Aalex (he/him)> This limit is pretty low for us It's the same for us. We are already looking ...

James•7/22/25, 5:51 PM

this was the main reason we didn't implement workflows, it wasn't much work to make something similar out of DOs and Queues that suits the same purpose and stateful guarantees.

Bboop Make the DO call a workflow, just use the DO alarms as a scheduler

Rahul gangotri•7/22/25, 6:11 PM

workflow has very weird bugs right now, all of my instances got queue and never got released, can't trust it right now

JJames this was the main reason we didn't implement workflows, it wasn't much work to m...

alex (he/him)•7/22/25, 6:29 PM

I would be interested how you use DOs to make something similar to Workflows

RRahul gangotri workflow has very weird bugs right now, all of my instances got queue and never ...

boop•7/22/25, 6:32 PM

I'm not too sure what this has to do with my suggestion

Elliot Hesp•7/22/25, 9:56 PM

Are there plans to get restart/pause etc working in local development?

alex (he/him)•7/23/25, 6:56 AM

And the most annoying part is actually, that running things locally with

wrangler dev

wrangler dev

does not have any limits in place, that means we can develop something which looks like it would work, but then it doesn't work at all in production, due to those limits only applying in production.

Vlad Lykhonis•7/23/25, 10:17 AM

It is been some time since I have posted regarding longer wall times for workflows. It seems quite random and eventually recovers, but consider my steps consist of simple few REST calls, it seems quite slow. Here is my latest instance for reference. I am not quite sure how to dig into this further to understand the possible cause of this.

Vlad Lykhonis•7/23/25, 10:19 AM

and right after it, I just ran more steps, and it was fast!

Aalex (he/him)So the fact that we also can't control concurrency on a per Workflow level means...

Vlad Lykhonis•7/23/25, 10:28 AM

Naturally I had the same first thought process - create many workflows, each workflow is small unit of work sequence. Then I saw limits in docs. Now, I rather pass batched arguments to fewer workflows and each workflow does a loop of steps per each unit of work sequence.

In the end it is not much of rework, and keeps it all still within limits and achiving same results.

This has been an issue forever. I have posted about it many times and others have experienced the sa

Similar Threads

Similar Threads

Similar Threads