Hi Gabriel. Could you provide more details here? Is this reoccurring for you? Which route are you hi

CCaio Hi Gabriel. Could you provide more details here? Is this reoccurring for you? Wh...

G

It is recurring, at least locally, when creating a workflow. My code is very simple:

    .post('/:integration/fetch', zValidator('param', z.object({ integration: z.string().min(1) })), async (ctx) => {
        const { integration } = ctx.req.valid('param')
        const instance = await ctx.env.HistoryIngestion.create({
            id: integration,
            params: { integrationId: integration },
        })
        await ctx.env.Jobs.put(
            `workflow:${integration}`,
            JSON.stringify({ instance: instance.id, status: 'pending', progress: 0, startedAt: Date.now() }),
        )
        return ctx.json({ success: true }, 202)
    })

    .post('/:integration/fetch', zValidator('param', z.object({ integration: z.string().min(1) })), async (ctx) => {
        const { integration } = ctx.req.valid('param')
        const instance = await ctx.env.HistoryIngestion.create({
            id: integration,
            params: { integrationId: integration },
        })
        await ctx.env.Jobs.put(
            `workflow:${integration}`,
            JSON.stringify({ instance: instance.id, status: 'pending', progress: 0, startedAt: Date.now() }),
        )
        return ctx.json({ success: true }, 202)
    })

    .post('/:integration/fetch', zValidator('param', z.object({ integration: z.string().min(1) })), async (ctx) => {
        const { integration } = ctx.req.valid('param')
        const instance = await ctx.env.HistoryIngestion.create({
            id: integration,
            params: { integrationId: integration },
        })
        await ctx.env.Jobs.put(
            `workflow:${integration}`,
            JSON.stringify({ instance: instance.id, status: 'pending', progress: 0, startedAt: Date.now() }),
        )
        return ctx.json({ success: true }, 202)
    })

    .post('/:integration/fetch', zValidator('param', z.object({ integration: z.string().min(1) })), async (ctx) => {
        const { integration } = ctx.req.valid('param')
        const instance = await ctx.env.HistoryIngestion.create({
            id: integration,
            params: { integrationId: integration },
        })
        await ctx.env.Jobs.put(
            `workflow:${integration}`,
            JSON.stringify({ instance: instance.id, status: 'pending', progress: 0, startedAt: Date.now() }),
        )
        return ctx.json({ success: true }, 202)
    })

M

meow•6/25/25, 4:40 AM

Hi, is there anyway to turn on verbose logging. I'm having some problem while building a crawler using workflows. While the links expand, it somehow leads to memory leak. Couldn't find the root cause for this.

entryErrorContext = jsgInternalError; wdErrId = cbiok85ihdsus98r7iao99nq
workerd/jsg/util.c++:320: error: e = workerd/util/sqlite.c++:499: failed: expected _ec ==
SQLITE_OK [7 == 0]; out of memory: SQLITE_NOMEM
stack:
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667f9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667c9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af50ab
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af4cee
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af49b8

entryErrorContext = jsgInternalError; wdErrId = cbiok85ihdsus98r7iao99nq
workerd/jsg/util.c++:320: error: e = workerd/util/sqlite.c++:499: failed: expected _ec ==
SQLITE_OK [7 == 0]; out of memory: SQLITE_NOMEM
stack:
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667f9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667c9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af50ab
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af4cee
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af49b8

entryErrorContext = jsgInternalError; wdErrId = cbiok85ihdsus98r7iao99nq
workerd/jsg/util.c++:320: error: e = workerd/util/sqlite.c++:499: failed: expected _ec ==
SQLITE_OK [7 == 0]; out of memory: SQLITE_NOMEM
stack:
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667f9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667c9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af50ab
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af4cee
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af49b8

entryErrorContext = jsgInternalError; wdErrId = cbiok85ihdsus98r7iao99nq
workerd/jsg/util.c++:320: error: e = workerd/util/sqlite.c++:499: failed: expected _ec ==
SQLITE_OK [7 == 0]; out of memory: SQLITE_NOMEM
stack:
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667f9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@2667c9d
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af50ab
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af4cee
./node_modules/@cloudflare/workerd-linux-64/bin/workerd@1af49b8

Original message was deleted

I

Idle•6/25/25, 9:51 AM

?pings

S

SuperHelpflare•6/25/25, 9:51 AM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

M

meow•6/25/25, 9:52 AM

Sorry

G

Gabriel Francisco•6/27/25, 11:31 PM

has anyone got "Worker exceeded CPU time limit." from workflows even that it is only waiting for TCP data and not performing any cpu task? (node:net socket)

GGabriel Francisco has anyone got "Worker exceeded CPU time limit." from workflows even that it is ...

K

koraytaylan•6/28/25, 9:59 AM

i believe you try to do some http calls not inside a step but within the main scope.

Kkoraytaylan i believe you try to do some http calls not inside a step but within the main sc...

G

Gabriel Francisco•6/28/25, 12:41 PM

its not the case. why would you think that?

GGabriel Francisco its not the case. why would you think that?

K

koraytaylan•6/28/25, 12:45 PM

because the whole point workflows (at least for me) is to not have any time limits. code running inside a step not supposed to have any such limits i believe. then i guess i would try splitting that specific step into multiple smaller ones to see it will still have this issue assuming the step being too big could be the reason.

Kkoraytaylan because the whole point workflows (at least for me) is to not have any time limi...

G

Gabriel Francisco•6/28/25, 1:15 PM

the problem is that the step is very small in code. but I receive tons of data via tcp

G

Gabriel Francisco•6/28/25, 1:16 PM

that was my assuption too, but my experience has been totally different

G

Gabriel Francisco•6/28/25, 1:16 PM

lots of silly limits

G

Gabriel Francisco•6/28/25, 1:17 PM

there is a very low memory limit (128mb), cpu time limit, http requests limit, even the quentity of active timers (setTimeouts)

G

Gabriel Francisco•6/28/25, 1:17 PM

very bad dx

G

Gabriel Francisco•6/28/25, 1:18 PM

and the cpu time limit I think its a bug on the node_compat of "node:net", no way I'm getting this limit from my code, it's probably internal

GGabriel Francisco there is a very low memory limit (128mb), cpu time limit, http requests limit, e...

K

koraytaylan•6/28/25, 1:20 PM

but receiving tons of data into memory is never a good idea anyway. for a similar case i stream the incoming data into an r2 object and then process it afterwards in a similar streaming fashion

GGabriel Francisco and the cpu time limit I think its a bug on the node_compat of "node:net", no wa...

K

koraytaylan•6/28/25, 1:21 PM

there is this new containers offering which is similarly in beta currently. from what you describe it seems like a better fit to me than workflows.

Kkoraytaylan but receiving tons of data into memory is never a good idea anyway. for a simila...

G

Gabriel Francisco•6/28/25, 1:26 PM

even if I stream the data to a r2 bucket I feel I will get the cpu limit

G

Gabriel Francisco•6/28/25, 1:26 PM

how do you process the data afterwards? using workflows?

Kkoraytaylan there is this new containers offering which is similarly in beta currently. from...

G

Gabriel Francisco•6/28/25, 1:27 PM

yep, I'm watching the containers 101 right now, that is my hypothesis too

G

Gabriel Francisco•6/28/25, 1:28 PM

but I feel very bad for workflows, I thought it was a better fit for use cases like mine, but with limits similar to workers http it makes it unusable for data management

M

meow•6/29/25, 4:29 PM

Hey guys, I’m trying to return workflow instance ids after createBatch. But the instance.id always return null. It works fine locally but not on production. Anyone experience this?

A

ac•6/29/25, 9:56 PM

Every time we end a workflow "early", e.g. just return a value before all the steps are done, this is logged as an Error in CF observability/logs section (even though it is definitely not an error). Is this a known issue? Will it be addressed?

W

Wilco•6/30/25, 7:40 AM

Hi all, I'm trying to catch an error from a step (when the retry limit is reached) and it seems the

cause

cause

of the error is not set. Is that expected? Makes it hard to communicate data from the failed step to the recovery flow

O

Olriko•6/30/25, 9:50 AM

Hello guys

I'm facing a problem where my workflow instances get queued but never starts. After a mistake that end up calling instances recursively.

OOlriko Hello guys I'm facing a problem where my workflow instances get queued but neve...

A

avenceslau•6/30/25, 9:51 AM

Please link your account so that we can have look

Aavenceslau Please link your account so that we can have look

O

Olriko•6/30/25, 9:54 AM

https://dash.cloudflare.com/e97e3fed722428f4d726062eae9aa766/workers/workflows

S

SODaLC•6/30/25, 12:36 PM

Is there a way to make Workflows process one at a time, instead of multiple running at once?

M

MithushanJ•6/30/25, 2:10 PM

What is the time limit for a step to finish in a workflow that has multiple steps

A

alex (he/him)•6/30/25, 6:07 PM

Any way we can get

step.waitForEvent

step.waitForEvent

not count towards the total step count per workflow, similar to

step.sleep

step.sleep

A

alex (he/him)•6/30/25, 6:08 PM

We have a hard time to strucutre our workflows to stay under the 1024 step limit. We either hit the cpu time limit of 5 minutes if we do multiple tasks in one step, or we hit the step limit if we do each task in a separate nested workflow

G

Gabriel Francisco•6/30/25, 6:52 PM

how can I see the logs of a specific instance? I can't find it on observability

A

alex (he/him)•6/30/25, 9:33 PM

Are memory limit of 128MB shared between multiple workflow instances?

A

alex (he/him)•7/1/25, 6:24 AM

What is the backoff rate from

exponential

exponential

is it 2?

Aac Every time we end a workflow "early", e.g. just return a value before all the st...

D

ddsgadget•7/1/25, 11:12 PM

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

S

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

A

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.

O

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

U

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 ?

M

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

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

D

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

G

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

G

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

M

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);

await this.env.WF_FILING_INGEST.createBatch(batchParams);

await this.env.WF_FILING_INGEST.createBatch(batchParams); and call their

status()

status()

status()

status() function?

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

B

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

J

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

Did you figure out what was going on?

B

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

A

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

J

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()"

Hi Gabriel. Could you provide more details here? Is this reoccurring for you? Which route are you hi

Similar Threads

Similar Threads

Similar Threads