Hi, does anyone know why I get this error even when my workflow completes succesfully? [ { me

Hi, does anyone know why I get this error even when my workflow completes succesfully?

[
{
message: 'run',
level: 'error',
$workers: {
event: { rpcMethod: 'run' },
scriptName: '----------',
outcome: 'exception',
eventType: 'rpc',
diagnosticsChannelEvents: [],
entrypoint: '---------,
scriptVersion: { id: '---------------------------- },
truncated: false,
executionModel: 'stateless',
wallTimeMs: 783,
cpuTimeMs: 10,
requestId: '------------------',
},
$metadata: {
id: '--------------------',
requestId: '-----------------',
trigger: 'default.run',
service: '--------------',
level: 'error',
error: 'run',
message: 'run',
account: '---------------------',
provider: 'cloudflare',
type: 'cf-worker-event',
fingerprint: '-----------------',
origin: 'rpc',
messageTemplate: 'run',
},
},
];

I can't catch any error to justify it

SSeekerdasbatatas This is an unfortunate side effect of how we guarantee durable execution, and we...

LuktarosOP•10/14/25, 7:33 PM

Oh, could this be the reason?

LLuktaros Oh, could this be the reason?

avenceslau•10/14/25, 7:52 PM

Yup we are working on it

Aavenceslau Yup we are working on it

LuktarosOP•10/14/25, 8:08 PM

Thank you so much for your answer, it was driving me crazy

, also let me add that I'm having a blast working with workflow

fredviken•10/14/25, 10:27 PM

would it be possible to use the waitForEvent to make a some sort of debounce?

oscar•10/16/25, 11:33 AM

Hello! Seeing a sharp rise on “internal workflows error” once again

DevZ•10/17/25, 3:42 PM

Hi guys, I need assistance to fix this issue: Too many API requests by single worker invocation. I have paid workers account. I am using Workflows alongside Queues to fetch, process, and store data.

daniel•10/18/25, 5:53 AM

hey is there a way to do per-user queues when triggering Workflows? Either natively within the Workflows or by using Queues to trigger workflows? I would like to be able to have per-user queues when triggering workflows via API but also when creating workflows from within another workflow

Tuna•10/18/25, 2:55 PM

Hey everyone!

Can someone help clarify how workflow memory and CPU limits are applied across steps and nested steps?
I’m trying to understand whether:
Each step gets its own CPU and memory allocation, or
Nested steps share the parent’s resource limits.
I tried looking this up in the docs, but the explanation wasn’t very clear. Any insights would be appreciated!

TrueBrain•10/19/25, 7:57 PM

Hello!

The Worker attached to a Workflow shows a lot more requests than the amount of invocations to the Workflow. Is this normal? Is this hibernation at work, or some other mechanism?
My workflow has a lot of sleep("10 minutes")sleep("10 minutes"), so I would assume it hibernates a lot

The docs state the pricing of a Workflow is per invocation; so can I ignore the amount of requests the Worker is showing me? Or are both charged? Or how does this work?

Any insights are appreciated

PS: possibly related, but there are also a lot of "cancelled" requests, the metrics tell me. Can't find any details on what "cancelled" means in this context.

Need_Not•10/21/25, 11:51 PM

It would be cool if workflows could emit data at each step

King Kazu•10/22/25, 10:29 PM

workflows would be great if there was local observability like how inngest has it

King Kazu•10/22/25, 10:30 PM

https://www.inngest.com/docs/local-development

King Kazu•10/22/25, 10:30 PM

makes it 10x easier to debug since its nearly impossible with cf workflows rn

KKing Kazu workflows would be great if there was local observability like how inngest has i...

xvvvyz•10/23/25, 5:05 AM

yes, please.

Deltachaos•10/23/25, 6:56 AM

In Workflows (using Python) i get this kind of exception:
"pyodide.ffi.JsException: Error: Too many API requests by single worker invocation."
Can someone explain to me what API requests are meant? API requests to external APIs using HTTP or API requests to cloudflare services or both?

Deltachaos•10/23/25, 10:50 AM

I would love to see a API to get the current limit usage dynamically (within a worker for example the amount of subrequests done)

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

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.

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

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

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)

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" });
  },
);

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 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 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?...

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

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

So that’s the correct value

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

Oh so even scheduled workers use workers.dev as upstream_zoneupstream_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...

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

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

I see in the docs that a step.sleepstep.sleep is a max duration of 365 days. Is waitForEventwaitForEvent 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?

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...

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...

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...

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

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...

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

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

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?

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

Yep, same as sleepsleep

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

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

Awesome. Thanks!

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

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...

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...

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...

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.

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...

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

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

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...

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...

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

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

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.

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?

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?

Hi, does anyone know why I get this error even when my workflow completes succesfully? [ { me

Similar Threads

Similar Threads

Similar Threads