I would love to see a API to get the current limit usage dynamically (within a worker for example th

SShivek 1000 total invocations. - I'm running a workflow that has many steps. - I need...

F

Focux•10/23/25, 1:31 PM

I just came to share this experience and found many comments saying the same. I hope they remove this limit for workers and add more built-in features, such as rate limiting, mechanisms to handle backpressure, child workflows, etc.

F

Focux•10/23/25, 1:31 PM

A

andrew•10/23/25, 7:02 PM

hello, we're heavy users of Workflows and our system is hitting up against the 100 per 10 seconds "Maximum Workflow instance creation rate" limit. we are seeing the number of queued workflow instances as we are adding users.

we've submitted the Limit Increase Request Form twice and wanted to see if someone could help with increasing our limit there

X

xvvvyz•10/23/25, 10:40 PM

need some help with this error if anyone can see something I can't

✘ [ERROR] TypeError: Cannot read properties of undefined (reading 'Symbol(Symbol.dispose)')

      at InstanceImpl.sendEvent
  (file:///Users/cade/Projects/api/node_modules/miniflare/dist/src/workers/workflows/wrapped-binding.worker.js:57:36)

✘ [ERROR] TypeError: Cannot read properties of undefined (reading 'Symbol(Symbol.dispose)')

      at InstanceImpl.sendEvent
  (file:///Users/cade/Projects/api/node_modules/miniflare/dist/src/workers/workflows/wrapped-binding.worker.js:57:36)

✘ [ERROR] TypeError: Cannot read properties of undefined (reading 'Symbol(Symbol.dispose)')

      at InstanceImpl.sendEvent
  (file:///Users/cade/Projects/api/node_modules/miniflare/dist/src/workers/workflows/wrapped-binding.worker.js:57:36)

✘ [ERROR] TypeError: Cannot read properties of undefined (reading 'Symbol(Symbol.dispose)')

      at InstanceImpl.sendEvent
  (file:///Users/cade/Projects/api/node_modules/miniflare/dist/src/workers/workflows/wrapped-binding.worker.js:57:36)

hono endpoint that triggers it

app.post(
  "/webhooks/modal/document-parsed",
  zValidator(
    "json",
    z.object({
      documentId: z.string(),
      instanceId: z.string(),
      markdown: z.string(),
      siteId: z.string(),
    }),
  ),
  async (c) => {
    const { documentId, instanceId, markdown, siteId } = c.req.valid("json");
    const instance = await c.env.DOCUMENT_WORKFLOW.get(instanceId);
    const key = `sites/${siteId}/files/${documentId}.md`;

    await c.env.R2.put(key, markdown, {
      httpMetadata: { contentType: "text/markdown" },
    });

    await instance.sendEvent({
      type: WorkflowEventType.DocumentParsed,
      payload: { markdownFileKey: key },
    });

    return c.json({ status: "ok" });
  },
);

app.post(
  "/webhooks/modal/document-parsed",
  zValidator(
    "json",
    z.object({
      documentId: z.string(),
      instanceId: z.string(),
      markdown: z.string(),
      siteId: z.string(),
    }),
  ),
  async (c) => {
    const { documentId, instanceId, markdown, siteId } = c.req.valid("json");
    const instance = await c.env.DOCUMENT_WORKFLOW.get(instanceId);
    const key = `sites/${siteId}/files/${documentId}.md`;

    await c.env.R2.put(key, markdown, {
      httpMetadata: { contentType: "text/markdown" },
    });

    await instance.sendEvent({
      type: WorkflowEventType.DocumentParsed,
      payload: { markdownFileKey: key },
    });

    return c.json({ status: "ok" });
  },
);

app.post(
  "/webhooks/modal/document-parsed",
  zValidator(
    "json",
    z.object({
      documentId: z.string(),
      instanceId: z.string(),
      markdown: z.string(),
      siteId: z.string(),
    }),
  ),
  async (c) => {
    const { documentId, instanceId, markdown, siteId } = c.req.valid("json");
    const instance = await c.env.DOCUMENT_WORKFLOW.get(instanceId);
    const key = `sites/${siteId}/files/${documentId}.md`;

    await c.env.R2.put(key, markdown, {
      httpMetadata: { contentType: "text/markdown" },
    });

    await instance.sendEvent({
      type: WorkflowEventType.DocumentParsed,
      payload: { markdownFileKey: key },
    });

    return c.json({ status: "ok" });
  },
);

app.post(
  "/webhooks/modal/document-parsed",
  zValidator(
    "json",
    z.object({
      documentId: z.string(),
      instanceId: z.string(),
      markdown: z.string(),
      siteId: z.string(),
    }),
  ),
  async (c) => {
    const { documentId, instanceId, markdown, siteId } = c.req.valid("json");
    const instance = await c.env.DOCUMENT_WORKFLOW.get(instanceId);
    const key = `sites/${siteId}/files/${documentId}.md`;

    await c.env.R2.put(key, markdown, {
      httpMetadata: { contentType: "text/markdown" },
    });

    await instance.sendEvent({
      type: WorkflowEventType.DocumentParsed,
      payload: { markdownFileKey: key },
    });

    return c.json({ status: "ok" });
  },
);

B

ByteBeast•10/24/25, 6:28 AM

Hello, I need one help. I have one workflow with some do steps, if any step got failed and it's maximum retry also got failed so can i retry it manually by any way? cloudflare doesn't provide API to retry specific step manually but by doing any hack can I achieve manual retry for any step?

D

D Trombett•10/25/25, 9:46 AM

Hey not sure if this is a bug or it's expected: Ruleset Engine docs specify that we can use

cf.worker.upstream_zone

cf.worker.upstream_zone

to identify if the request comes from a Worker but I noticed that this value is empty when the request is from a Workflow. I'm using this to allow requests to a host only to subrequests from my own workers (and thus Workflows)

D

D Trombett•10/25/25, 10:04 AM

Oh wait after investigating a bit I think that the value is not empty but wrong? Instead of my zone (example.com), like requests from my worker, CF-Worker is set to example.workers.dev which doesn't really make sense since my dev url is disabled

DD Trombett Oh wait after investigating a bit I think that the value is not empty but wrong?...

H

Hello, I’m Allie!•10/25/25, 7:07 PM

IIRC that’s what it is set for all requests from Worker Events that aren’t fetches on a zone

H

Hello, I’m Allie!•10/25/25, 7:07 PM

So that’s the correct value

D

D Trombett•10/25/25, 7:13 PM

Oh so even scheduled workers use workers.dev as

upstream_zone

upstream_zone

? Well, if it's expected is ok, I can still match them with my workers.dev domain, thanks a lot!

DD Trombett Oh so even scheduled workers use workers.dev as `upstream_zone`? Well, if it's e...

H

Hello, I’m Allie!•10/25/25, 8:01 PM

Yeah, all Workers have some kind of upstream zone set, so that you can filter on them. If there are any that don’t, that would be a bug

H

Hunter Bertoson•10/27/25, 9:32 PM

I see in the docs that a

step.sleep

step.sleep

is a max duration of 365 days. Is

waitForEvent

waitForEvent

also that long? Does it have a default timeout if I do not specify one? Or will it literally just wait until the end of time?

D

Directortime•10/27/25, 9:46 PM

I need a server to be put together also a site running on cloudflar dNS is giving a issue.

DDirectortime I need a server to be put together also a site running on cloudflar dNS is givin...

1

1984 Ford Laser•10/27/25, 10:38 PM

Try in #general-discussions or #general-help this isn't the right channel for help with DNS

HHunter Bertoson I see in the docs that a `step.sleep` is a max duration of 365 days. Is `waitFor...

M

Matt Silverlock•10/28/25, 12:33 PM

cc @mia

DDeltachaos I would love to see a API to get the current limit usage dynamically (within a w...

M

Matt Silverlock•10/28/25, 12:34 PM

We’re planning on dramatically increasing this limit (10k+ or even higher) for all paid users very shortly. Within next 2-3 weeks, if not sooner.

MMatt Silverlock cc @mia

H

Hunter Bertoson•10/28/25, 12:42 PM

For some context.

I’m using the waitForEvent for a webhook. And it could be an unknown amount of time before I get that webhook event. It won’t be a year lol. But just wasn’t sure if it had a default timeout that I needed to be aware of.

HHunter Bertoson For some context. I’m using the waitForEvent for a webhook. And it could be an...

M

Matt Silverlock•10/28/25, 12:49 PM

24 hours. You can change that per the docs. Updating to also clarify the default there.

H

Hunter Bertoson•10/28/25, 12:50 PM

Good to know. Thanks! What’s the max time? 365 days?

HHunter Bertoson Good to know. Thanks! What’s the max time? 365 days?

M

Matt Silverlock•10/28/25, 12:52 PM

Yep, same as

sleep

sleep

M

Matt Silverlock•10/28/25, 12:52 PM

https://github.com/cloudflare/cloudflare-docs/pull/26112/files#diff-ba9520ec521be85b85e362a1590ea0f55e03bf5b15f71865e1df1c2d5e7cbafc

GitHub

workflows: Clarify timeout default by elithrar · Pull Request #261...

Clarify the default timeout of waitForEvent

H

Hunter Bertoson•10/28/25, 12:54 PM

Awesome. Thanks!

Started using workflows in this project and they are so cool. Great job!

S

SODaLC•10/28/25, 2:11 PM

Are there any rules/consequence to using while loops in a step?

I want to retry a step but have timers that are dynamic and ever changing so wouldnt really work with the workflow step auto retry config. So i plan to sleep inside a while loop but unsure whether this would have unforeseen consequence as there is no documentation on this type of pattern?

SSODaLC Are there any rules/consequence to using while loops in a step? I want to retr...

M

Matt Silverlock•10/28/25, 4:45 PM

It’s just code. As long as you don’t run into step limits, it doesn’t matter what flow control you use.

SSODaLC Are there any rules/consequence to using while loops in a step? I want to retr...

M

Matt Silverlock•10/28/25, 4:46 PM

Something like p-map can be useful if you care about concurrency over a bunch of async tasks + simplifies failure handling: https://www.npmjs.com/package/p-map

but if you just need a while loop, use a while loop!

SSODaLC Are there any rules/consequence to using while loops in a step? I want to retr...

M

Matt Silverlock•10/28/25, 4:48 PM

Just note that (this is not specific to Workflows) that

while (condition) { await step.do(...) }

while (condition) { await step.do(...) }

will block on each

await

await

before it iterates.

X

xenophyte1234•10/29/25, 3:53 AM

question about waitForEvent, sometimes, even the event is fired, the waitForEvent is still waiting. This happens to the workflow that has waited for more than 20 minutes, do I miss something? Is it because I put the waitForEvent inside a step.do?

Xxenophyte1234 question about waitForEvent, sometimes, even the event is fired, the waitForEven...

H

Hunter Bertoson•10/29/25, 4:09 AM

Could be. I would not do that. waitForEvent is its own step.

O

Olriko•10/29/25, 8:49 AM

Hello, there is a plan to support the new framework https://useworkflow.dev/ ?

Workflow DevKit - Make any TypeScript Function Durable

"use workflow" brings durability, reliability, and observability to async JavaScript. Build apps and AI Agents that can suspend, resume, and maintain state with ease.

MMatt Silverlock Just note that (this is not specific to Workflows) that `while (condition) { awa...

S

SODaLC•10/29/25, 12:53 PM

it does sound so simple after saying that. I was just more worried about how the workflow would resume if sleeping inside a while loop and if i would encounter potential billing runaways from the loops.

MMatt Silverlock Something like p-map can be useful if you care about concurrency over a bunch of...

S

SODaLC•10/29/25, 12:57 PM

now that is pretty cool, definitely useful for my project, thanks

X

xvvvyz•10/29/25, 8:07 PM

what is the expected behavior when you terminate a workflow?

it says it's not implemented locally, and in cloudflare steps continue to run.

couldn't find details in the docs.

L

Lulu•10/29/25, 8:57 PM

So I am really confused about the use cases of Workflows vs Queues. Seems like anything you could do in one you could also do in the other. Are there specific parameters (like limits, costs, performance, etc.) that I should keep in mind when deciding?

P

Paul•10/29/25, 9:34 PM

I have a pattern I'm using now where a Consuming Worker is pulling events off a Queue and then it just starts a Workflow. Are there plans to support Workflows as Queue consumers, so we can drop the consuming Worker form the flow?

OOlriko Hello, there is a plan to support the new framework https://useworkflow.dev/ ?

P

Paul•10/29/25, 9:52 PM

That framework looks really interesting, but it wasn't clear reading the site, does this have some kind of bridge to Cloudflare Workflows? Maybe I missed it, but I was hoping there was some kind of way to just deploy your Typescript funciton into a Cloudflare Workflow?

V

vijayaraagavan•10/30/25, 7:19 AM

How to get updates from workflow other than polling? Does polling every second cause rate limiting?

Vvijayaraagavan How to get updates from workflow other than polling? Does polling every second c...

1

1984 Ford Laser•10/30/25, 9:03 AM

You could have the Workflow send an event to a Worker or something to track updates

T

Tuna•10/30/25, 9:31 AM

can i call a workflow from a step inside a workflow??

D

D Trombett•10/30/25, 9:35 AM

Yes

A

ajay | dreamlit.ai•10/30/25, 2:56 PM

Hey @avenceslau We have been encountering Workflow instances that occasionally are terminating on their own while running and aren't throwing an error as expected. It seems to occur about once a day now, and it requires manual intervention for us to kick the workflow off again.

Essentially these Workflow instances appear to be receiving a "terminate" signal but we are not the ones initiating them. Any idea on what might be up?

S

scook•10/30/25, 7:40 PM

Correct me if I'm wrong, but is there really not a way to use wrangler CLI to trigger a workflow for local dev??

J

jepcd•10/31/25, 12:49 AM

minor suggestion: display error messages on the dashboard/api

currently, a

throw new NonRetryableError("File too big!")

throw new NonRetryableError("File too big!")

throw new NonRetryableError("File too big!")

throw new NonRetryableError("File too big!")

just shows up as

The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled

The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled

The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled

The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled

PPaul That framework looks really interesting, but it wasn't clear reading the site, d...

O

Olriko•10/31/25, 10:58 AM

No bridge to Cloudflare Workflows currently exists, but since the framework is open source, a Cloudflare world (https://useworkflow.dev/docs/deploying/world) is possible. Imo, the syntax is cleaner than the current CF class approach.

N

Nathan Scheele•10/31/25, 3:47 PM

I started getting the following error when sending events to a Workflow Instance that is waiting. See attached for implementation of waitForEvent and sendEvent. This setup has been working fine up until now. This seems to only be an issue locally; deployed versions are working as expected.

error.txt877B

sendEvent.ts147B

waitForEvent.ts185B

OOlriko No bridge to Cloudflare Workflows currently exists, but since the framework is o...

P

Paul•10/31/25, 3:50 PM

My analysis indicates it's not a fit.

cloudflare-adapter-analysis.pdf1.56MB

J

jepcd•11/1/25, 12:16 AM

I'm seeing a lot of persistent internal server errors when accessing the workflows dashboard.

Additionally, some steps still show as running, around 20 minutes after I terminated the instance. Is that expected?

fwiw this was probably caused by some bad workflow code I was testing that causes the step hang, but I wouldn't expect the dashboard to internal server error.

Instance ID: 1ededc19-f498-4e11-947d-b3cbb507cf18

S

Sathyamshu•11/1/25, 12:29 AM

Why is there a limit for the concurrent workflow invocations (10k)

This blocks the things a lot.

Assume a workflow is used to remind after 30 days sign-up.
If 10k users sign up in a day or week...

That's it.. can't invoke any other workflow.

Is there any solution for this??
How to approach this kindaa things?
Or
Is it better to implement on own using workers and some other ?,

SSathyamshu Why is there a limit for the concurrent workflow invocations (10k) This blocks ...

1

1984 Ford Laser•11/1/25, 12:40 AM

You could combine with Queues for batching and delays

SSathyamshu Why is there a limit for the concurrent workflow invocations (10k) This blocks ...

S

Seekerdasbatatas•11/1/25, 10:45 AM

If an instance is in a

waiting

waiting

waiting

waiting state (following your example, sleeping for 30 days), it does not count towards the concurrent invocation limit - only instances with a

running

running

running

running state will count towards the limit

SSeekerdasbatatas If an instance is in a `waiting` state (following your example, sleeping for 30 ...

S

Sathyamshu•11/1/25, 12:32 PM

okay...got it...!

but still, why is there a limit? can't they be just like the workers with no concurrent limits for invocations/executions?

Am I thinking right??

I would love to see a API to get the current limit usage dynamically (within a worker for example th

Similar Threads

Similar Threads

Similar Threads