is it possible to see logs created by "console.log" in the steps somewhere?

D

DeltachaosOP•3/31/25, 9:34 AM

and i dont see any information about what the limits for workflows are in the free tier?

D

DeltachaosOP•3/31/25, 12:09 PM

and is it possible to use workflows with python or rust?

DDeltachaos is it possible to see logs created by "console.log" in the steps somewhere?

M

Matt Silverlock•3/31/25, 12:12 PM

Logs are emitted here: https://developers.cloudflare.com/workers/observability/logs/workers-logs/

Cloudflare Docs

Workers Logs · Cloudflare Workers docs

Store, filter, and analyze log data emitted from Cloudflare Workers.

DDeltachaos and i dont see any information about what the limits for workflows are in the fr...

M

Matt Silverlock•3/31/25, 12:12 PM

All limits are here: https://developers.cloudflare.com/workflows/reference/limits/

Cloudflare Docs

Limits · Cloudflare Workflows docs

Limits that apply to authoring, deploying, and running Workflows are detailed below.

MMatt Silverlock Logs are emitted here: https://developers.cloudflare.com/workers/observability/l...

D

DeltachaosOP•3/31/25, 12:13 PM

also for console.logs from workflows?

M

Matt Silverlock•3/31/25, 12:13 PM

Yes.

MMatt Silverlock FYI for those of you with longer-running Workflows: we've increased the maximum ...

G

gruntlord6•4/1/25, 1:02 AM

I forgot this happened, thanks! That helps with a large file I have to process and was difficult to split among workers

A

adeola13.•4/1/25, 7:00 PM

Has anybody been able to successfully debug workflows locally in vscode with breakpoints?

For regular workers my local debugging with breakpoints works great, but with workflows It always crashes:

✘ [ERROR] workerd/jsg/setup.c++:39: fatal: V8 fatal error; location = :0; message = Check failed: needs_context && current_scope_ == closure_scope_ && current_scope_->is_function_scope() && !function_.is_null() implies function_->context() != *context_.

  *** Received signal #6: Abort trap: 6
  stack:

✘ [ERROR] workerd/jsg/setup.c++:39: fatal: V8 fatal error; location = :0; message = Check failed: needs_context && current_scope_ == closure_scope_ && current_scope_->is_function_scope() && !function_.is_null() implies function_->context() != *context_.

  *** Received signal #6: Abort trap: 6
  stack:

✘ [ERROR] workerd/jsg/setup.c++:39: fatal: V8 fatal error; location = :0; message = Check failed: needs_context && current_scope_ == closure_scope_ && current_scope_->is_function_scope() && !function_.is_null() implies function_->context() != *context_.

  *** Received signal #6: Abort trap: 6
  stack:

✘ [ERROR] workerd/jsg/setup.c++:39: fatal: V8 fatal error; location = :0; message = Check failed: needs_context && current_scope_ == closure_scope_ && current_scope_->is_function_scope() && !function_.is_null() implies function_->context() != *context_.

  *** Received signal #6: Abort trap: 6
  stack:

M

Marco Aleixo•4/2/25, 2:10 AM

I really want to be able to delete workflows

MMatt Silverlock We’re working on a waitForEvent API that should land very soon.

F

Frederik•4/2/25, 2:50 AM

Is there a roadmap for upcoming workflow features? Something that is a bit more precisely than ‚very soon’? I‘m missing waitForEvent as well. By now it looks like it is the only missing pease which prevents me from really using it. Waiting for event signals is something which works really nice with temporal.io and I would love to see something similar in cloudflare workflows.

FFrederik Is there a roadmap for upcoming workflow features? Something that is a bit more ...

M

Matt Silverlock•4/2/25, 10:28 AM

In the next couple of weeks or so.

FFrederik Is there a roadmap for upcoming workflow features? Something that is a bit more ...

M

Matt Silverlock•4/2/25, 10:29 AM

We don’t provide precise dates as things change / sometimes need to be prioritized - e.g. solving a customer issue or another key ask!

Aadeola13.Has anybody been able to successfully debug workflows locally in vscode with bre...

S

Seekerdasbatatas•4/2/25, 11:10 AM

I've reported the issue to the team

if you wish, feel free to open an issue about this in the
```
workers-sdk
```
workers-sdk
```
workers-sdk
```
workers-sdk
repo

J

juanferreras•4/2/25, 1:31 PM

it might be my own fault but whilst I've been loving the capabilities of workflows (and they might just be my fav new primitive) – last night it's been the 2nd time I've been running into issues troubleshooting errors whilst developing them (once deployed).

unless last night there were some internal issues?

Attempt failed due to internal workflows error

Attempt failed due to internal workflows error

Attempt failed due to internal workflows error

Attempt failed due to internal workflows error just realized I had some of the errored throwing that err

J

juanferreras•4/2/25, 1:44 PM

but other runs last night also just timed out errorless. Seems that today the same code is working perfectly. I had a similar experience a few days ago trying to convert a workflow that does...

try { await step.do("first step") } catch { ... }
try { await step.do("second step") } catch { ... }
try { await step.do("third step") } catch { ... }

try { await step.do("first step") } catch { ... }
try { await step.do("second step") } catch { ... }
try { await step.do("third step") } catch { ... }

try { await step.do("first step") } catch { ... }
try { await step.do("second step") } catch { ... }
try { await step.do("third step") } catch { ... }

try { await step.do("first step") } catch { ... }
try { await step.do("second step") } catch { ... }
try { await step.do("third step") } catch { ... }

into something that just fired the three in parallel.

It's +95% likely that I'm doing things wrong but wanted to share in case it's helpful feedback or there are some tips I might have missed from docs

Jjuanferreras it might be my own fault but whilst I've been loving the capabilities of workflo...

S

Seekerdasbatatas•4/2/25, 4:27 PM

could you get me your account id please? so that I can look into this futher

Jjuanferreras but other runs last night also just timed out errorless. Seems that today the sa...

S

Seekerdasbatatas•4/2/25, 4:27 PM

a reproducible example would be helpful here, as there are (unfortunately - because JS is weird) to make many steps run in parallel

M

Marc•4/2/25, 11:21 PM

Is it possible to extend the NonRetryableError into a custom error while maintining it's workflow ending power? Because this doesn't seem to work:

class EndWorkflowError extends NonRetryableError {
    event: WorkflowEvent<Params>;
    shouldFallback: boolean;

    constructor(data: {
        message: string;
        error: unknown;
        event: WorkflowEvent<Params>;
        shouldFallback?: boolean;
    }) {
        super(data.message);
        this.name = 'EndWorkflowError';
        this.message = data.message;
        this.event = data.event;
        this.cause = data.error;
        this.shouldFallback = data.shouldFallback === undefined ? true : data.shouldFallback;
    }
}

class EndWorkflowError extends NonRetryableError {
    event: WorkflowEvent<Params>;
    shouldFallback: boolean;

    constructor(data: {
        message: string;
        error: unknown;
        event: WorkflowEvent<Params>;
        shouldFallback?: boolean;
    }) {
        super(data.message);
        this.name = 'EndWorkflowError';
        this.message = data.message;
        this.event = data.event;
        this.cause = data.error;
        this.shouldFallback = data.shouldFallback === undefined ? true : data.shouldFallback;
    }
}

class EndWorkflowError extends NonRetryableError {
    event: WorkflowEvent<Params>;
    shouldFallback: boolean;

    constructor(data: {
        message: string;
        error: unknown;
        event: WorkflowEvent<Params>;
        shouldFallback?: boolean;
    }) {
        super(data.message);
        this.name = 'EndWorkflowError';
        this.message = data.message;
        this.event = data.event;
        this.cause = data.error;
        this.shouldFallback = data.shouldFallback === undefined ? true : data.shouldFallback;
    }
}

class EndWorkflowError extends NonRetryableError {
    event: WorkflowEvent<Params>;
    shouldFallback: boolean;

    constructor(data: {
        message: string;
        error: unknown;
        event: WorkflowEvent<Params>;
        shouldFallback?: boolean;
    }) {
        super(data.message);
        this.name = 'EndWorkflowError';
        this.message = data.message;
        this.event = data.event;
        this.cause = data.error;
        this.shouldFallback = data.shouldFallback === undefined ? true : data.shouldFallback;
    }
}

M

mrv•4/4/25, 12:01 AM

I have some workflows that became orphaned after their associated workers were deleted. Is it possible to delete them somehow?

T

tadhglewis•4/4/25, 10:11 AM

@mrv it's not possible to delete workflows at all currently

JJonathan Lister Parsons Is there a recommendation about how to get a front-end web client to invoke Work...

S

Seekerdasbatatas•4/4/25, 12:57 PM

my recommendation is always the latter, you shouldn't expose Cloudflare API tokens directly to users and instead maybe create your own (maybe by using auth providers, like clerk and so on) - so that you can also have proper validation in your endpoints too

SSeekerdasbatatas my recommendation is always the latter, you shouldn't expose Cloudflare API toke...

M

Matt Silverlock•4/4/25, 1:40 PM

Strongly agree here. If you need client side authentication, use a library or tooling that’s appropriate for that + gives you the controls that allow you to scope access precisely

M

Matt Silverlock•4/4/25, 1:41 PM

That will also allow you rate limit clients, emit metrics to Analytics Engine, validate payloads, etc - before they hit the workflow

M

Marc•4/4/25, 3:10 PM

Suddenly whenever my worker invokes my workflow I am getting a 500 error (Error: internal error {} )

I've tried looking all over for a better error log to explain what's going on but so far can't get it to tell me. If I wrap the workflow create call in a try catch all I get is the above error.

My only slight lead is that maybe this started to happen after I tried to cross script bind the workflow to another worker, but that's not the script I'm calling this one from. Could a bad binding to something else be messing up this binding?

Any leads on where to get a better error message on what's wrong or is there something going on with workflows?

J

Justin•4/4/25, 8:24 PM

What's the best practice for making a workflow step conditional?

Like, can I do the following to skip a step entirely?

const shouldHappen = await step.do('check condition', async () => { return false })
if (shouldHappen) {
  await step.do('conditional step', async () => { //do something })
}

const shouldHappen = await step.do('check condition', async () => { return false })
if (shouldHappen) {
  await step.do('conditional step', async () => { //do something })
}

const shouldHappen = await step.do('check condition', async () => { return false })
if (shouldHappen) {
  await step.do('conditional step', async () => { //do something })
}

const shouldHappen = await step.do('check condition', async () => { return false })
if (shouldHappen) {
  await step.do('conditional step', async () => { //do something })
}

Or, should I evaluate the condition within a step, like this?

const shouldHappen = await step.do('check condition', async () => { return false })
await step.do('conditional step', async () => {
  if (!shouldHappen) return
  //do something
})

const shouldHappen = await step.do('check condition', async () => { return false })
await step.do('conditional step', async () => {
  if (!shouldHappen) return
  //do something
})

const shouldHappen = await step.do('check condition', async () => { return false })
await step.do('conditional step', async () => {
  if (!shouldHappen) return
  //do something
})

const shouldHappen = await step.do('check condition', async () => { return false })
await step.do('conditional step', async () => {
  if (!shouldHappen) return
  //do something
})

JJustin What's the best practice for making a workflow step conditional? Like, can I do...

M

Matt Silverlock•4/5/25, 12:53 PM

I like to say: Workflows are just code. Call steps conditionally, use Promise.all or p-map or (etc) to run steps concurrently.

step

step

step

step methods are just async function calls at the end of the day.

D

dragonli•4/6/25, 12:27 AM

Is there anyone who knows how to make the workflow execute immediately?

I found that there seems to be a delay between triggering the creation of a workflow from a worker and the actual execution of the workflow.

According to the test, it is close to 4 or 5 seconds. How can I make the workflow execute immediately?

D

dragonli•4/6/25, 12:31 AM

Currently, I'm triggering workflows via webhooks and want them to execute as quickly as possible. Should I switch to long-polling an API within the workflow instead? Is this usage considered a best practice?

K

Kiwi•4/6/25, 3:54 AM

I'm also seeing this from my RPC call to workflow spin up being quite slow. It is so slow that I'm actually going to bring that code back into my request flow as it will be on the whole quicker.

KKiwi I'm also seeing this from my RPC call to workflow spin up being quite slow. It i...

M

Matt Silverlock•4/7/25, 11:01 AM

What do you define as slow here? Workflows are designed for async tasks, so if you’re trying to run something that only takes a few seconds it may not make sense. But the Workflow itself should fire off quickly, provided you aren’t at concurrency limits.

FFrederik Is there a roadmap for upcoming workflow features? Something that is a bit more ...

M

Matt Silverlock•4/7/25, 12:48 PM

step.waitForEvent

step.waitForEvent

step.waitForEvent

step.waitForEvent

https://developers.cloudflare.com/workflows/build/events-and-parameters/#wait-for-events

M

Matt Silverlock•4/7/25, 1:33 PM

@Workflows - Workflows is GA + we've shipped the new

step.waitForEvent

step.waitForEvent

step.waitForEvent

step.waitForEvent (and

instance.sendEvent

instance.sendEvent

instance.sendEvent

instance.sendEvent) APIs! https://blog.cloudflare.com/workflows-ga-production-ready-durable-execution/

The Cloudflare Blog

Cloudflare Workflows is now GA: production-ready durable execution

Workflows — a durable execution engine built directly on top of Workers — is now Generally Available. We’ve landed new human-in-the-loop capabilities, more scale, and more metrics: just what you need for a production-ready service.

J

Jadugar_Jaggu•4/7/25, 5:38 PM

it seems workflows are little bit slower today?

JJadugar_Jaggu it seems workflows are little bit slower today?

S

Seekerdasbatatas•4/7/25, 6:35 PM

slower in what sense? if it's because of instance creation, you might be creating too many instances in short periods of time which have a higher load - I would recommend looking into

createBatch

createBatch

createBatch

createBatch to reduce the number of calls, if that applies to your usecase

SSeekerdasbatatas slower in what sense? if it's because of instance creation, you might be creatin...

J

Jadugar_Jaggu•4/7/25, 6:36 PM

No it's in the sense of performance, previously my workflows were taking 8 to 15 minutes to complete now they are taking almost 40 minutes +

J

Jadugar_Jaggu•4/7/25, 6:36 PM

maybe a hour

JJadugar_Jaggu No it's in the sense of performance, previously my workflows were taking 8 to 15...

S

Seekerdasbatatas•4/7/25, 6:39 PM

they are taking that time from running to a completed state or from a queued state to a complete one? anyway can we have your account id so we can look at it?

SSeekerdasbatatas they are taking that time from running to a completed state or from a queued sta...

J

Jadugar_Jaggu•4/7/25, 6:43 PM

For running to completed state. sent you I'd in DM

J

Jadugar_Jaggu•4/7/25, 6:44 PM

not able to DM you

S

Suman!•4/7/25, 7:21 PM

Hey guys,
I am getting an error when using this new Workflow API sendEvent in the production environment. Local works as expected.

const workflow = await this.env.CONNECTIONS_WORKFLOW.get(workflowId);
    await workflow.sendEvent({ type: 'form-submission', payload });

const workflow = await this.env.CONNECTIONS_WORKFLOW.get(workflowId);
    await workflow.sendEvent({ type: 'form-submission', payload });

const workflow = await this.env.CONNECTIONS_WORKFLOW.get(workflowId);
    await workflow.sendEvent({ type: 'form-submission', payload });

const workflow = await this.env.CONNECTIONS_WORKFLOW.get(workflowId);
    await workflow.sendEvent({ type: 'form-submission', payload });

Error message:

TypeError: (intermediate value).sendEvent is not a function

TypeError: (intermediate value).sendEvent is not a function

TypeError: (intermediate value).sendEvent is not a function

TypeError: (intermediate value).sendEvent is not a function

A

Adrien•4/7/25, 7:45 PM

Hey and congrats for GA

!
Is it possible to have an in-progress state that could be queried? In the case of an onboarding workflow, while we wait on a specific outside event, we can fetch the status of the workflow and some arbitrary data. Maybe similar to Temporal Query feature?

SSuman!Hey guys, I am getting an error when using this new Workflow API sendEvent in th...

J

Jadugar_Jaggu•4/7/25, 7:52 PM

update your project wrangler version

JJadugar_Jaggu update your project wrangler version

S

Suman!•4/7/25, 7:53 PM

I think it's already at its peak