Sure, that’s fine. Though, even if it doesn’t need to hit an external service, if it performs a lot

Sure, that’s fine. Though, even if it doesn’t need to hit an external service, if it performs a lot of work, I would still persist it

SODaLC•6/17/25, 3:36 PM

Is the first message in a workflow log suppose to be an error, or have I done something wrong? The rest of the code executes just fine.

DDan (Openside)When architecting workflows and steps, what are the pros/cons of using a queue i...

Dan (Openside)•6/17/25, 10:20 PM

curious if any Cloudflare team members have thoughts on this.

gamarra2042•6/18/25, 11:10 AM

anyone having problem with workflows today? instances all on queue and not running

Cristian Lipinski•6/18/25, 12:30 PM

Hello guys

Im facing a problem where my workflow instances get queued but never starts

This started may 15th, on that time, I noticed that when we manually paused some wf queued instance, all instances above it were triggered

then I publised a worker that basically start, pause, and finish a wf instance so my routines could be triggered

That worked until today (June 18th); this morning, none of my instances are being triggered, even with that start/pause “quick fix”

There are some crucial routines to our company, i'm even thinking about trying to migrate those routines to other account or even service

We're using a lot of cloudflare services and investing around 4.5k usd monthly

Could anyone help me with that matter?

HHello, I’m Allie!Sure, that’s fine. Though, even if it doesn’t need to hit an external service, i...

alex (he/him)•6/18/25, 2:01 PM

True. But an sdk client or a zod validator isn’t serializiable anyway, right?

TTobias Is it possible to set concurrency limits on a workflow? Kind of like how Trigger...

ItsWendell•6/18/25, 6:42 PM

Do we have any updates on this? I'm building a complicated queue with durable workers now as a workaround but this would make it easier

Gabriel Francisco•6/18/25, 7:59 PM

hey, how cloudflare workers with multiple environments deal with workflows?

Gabriel Francisco•6/18/25, 8:00 PM

should I put one workflow at the root of the wrangler.toml or should I create a workflow for each env?

Gabriel Francisco•6/18/25, 8:00 PM

the first one seems more correct but it produces a warning

Aalex (he/him)True. But an sdk client or a zod validator isn’t serializiable anyway, right?

Hello, I’m Allie!OP•6/19/25, 3:28 AM

I would think they are? Since they are still JS objects? Might be a case of try and see?

GGabriel Francisco should I put one workflow at the root of the wrangler.toml or should I create a ...

ddsgadget•6/19/25, 10:53 AM

You should have a separate workflow for each environment. Just change the name of the specific workflow in the wrangler.toml for each environment and leave everythng else the same in the workflow definition in the toml and it will work. Cloudflare will build a separate workflow for each environment using the same exact class. hpe that makese sense

Dddsgadget You should have a separate workflow for each environment. Just change the name o...

Gabriel Francisco•6/19/25, 2:07 PM

thank you! very helpful!

nicoritschel•6/19/25, 2:29 PM

Are containers still landing this month?

Marco Aleixo•6/19/25, 5:37 PM

hey team - I have almost 500 workflows stuck as running status ( without steps ) for almost 5 days

Gabriel Francisco•6/20/25, 3:15 PM

have anyone got "An RPC result was not disposed properly" when calling a workflow from a hono route?

Gabriel Francisco•6/20/25, 3:15 PM

there is no disposables at this flow, but I keep getting this error

GGabriel Francisco have anyone got "An RPC result was not disposed properly" when calling a workflo...

koraytaylan•6/20/25, 7:26 PM

could it be that you do not await the create call to finish before exiting the hono route?

Kkoraytaylan could it be that you do not await the create call to finish before exiting the h...

Gabriel Francisco•6/20/25, 9:19 PM

good hypothesis, but its not that

Gabriel Francisco•6/20/25, 9:19 PM

I use the instance id, right after too, ensuring the create is awaited

Gabriel Francisco•6/20/25, 9:20 PM

it seems like a bug on hono or workflows

Elsa k🦮•6/20/25, 9:20 PM

Yes

rbravo•6/21/25, 1:55 AM

Hey, If I have a WF instance that has a sleepUntil, and I use .terminate it should cancel all the following executions that are inside this workflow, right? Right now even if I terminate the instance it keeps the execution.

GGabriel Francisco have anyone got "An RPC result was not disposed properly" when calling a workflo...

Caio•6/23/25, 9:44 AM

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

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

Gabriel Francisco•6/23/25, 1:14 PM

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

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

Original message was deleted

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

?pings

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.

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

Sorry

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

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

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?

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

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

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

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

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

lots of silly limits

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)

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

very bad dx

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

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

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

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

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

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

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

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

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?

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?

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 causecause of the error is not set. Is that expected? Makes it hard to communicate data from the failed step to the recovery flow

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

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

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

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

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

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

Sure, that’s fine. Though, even if it doesn’t need to hit an external service, if it performs a lot

Similar Threads

Similar Threads

Similar Threads