I am looping over a json array. each step does some api calls and changes the item inside the json.

AAdvany I am looping over a json array. each step does some api calls and changes the it...

H

Hello, I’m Allie!•3/19/25, 2:42 PM

What do the steps in the loop return?

MMatt Silverlock Timeout is per step... with `20160` total retries before it will terminally fail...

A

ajay | dreamlit.ai•3/19/25, 2:50 PM

Right, we should have expected retry functionality there correct? It appears that it was in that stuck in that

Running

Running

Running

Running state. When I queried for the events for this instanceId via the GraphQL analytics API - there was only 1 ATTEMPT_START for that ID, I do not see that any retries were executed.

Even after I terminated the instance, while the workflow run changed the status to

Terminated

Terminated

Terminated

Terminated, the step status still says

Running

Running

Running

Running. See screenshot. Perhaps I've misconfigured something?

Thank you for your help!

HHello, I’m Allie!What do the steps in the loop return?

A

AdvanyOP•3/20/25, 12:29 PM

fixed it! I make the loop part of a bigger step and get and set base don that!

O

omar•3/20/25, 1:28 PM

I'm getting an error fetching a file from R2 within my workflow

[ERROR] Uncaught (in promise) DOMException

[ERROR] Uncaught (in promise) DOMException

[ERROR] Uncaught (in promise) DOMException

[ERROR] Uncaught (in promise) DOMException

  const file = await step.do("get file from R2", async () => {
    return this.env.STATEMENT_BUCKET.get(fileIdentifier)
  });

  const file = await step.do("get file from R2", async () => {
    return this.env.STATEMENT_BUCKET.get(fileIdentifier)
  });

  const file = await step.do("get file from R2", async () => {
    return this.env.STATEMENT_BUCKET.get(fileIdentifier)
  });

  const file = await step.do("get file from R2", async () => {
    return this.env.STATEMENT_BUCKET.get(fileIdentifier)
  });

Oomar I'm getting an error fetching a file from R2 within my workflow ```[ERROR] Uncau...

H

Hello, I’m Allie!•3/20/25, 1:34 PM

I’m guessing that’s probably because an R2 file is not serializable

J

JMPA•3/20/25, 9:17 PM

do you know where can i found a example code with impaiting working?

J

JMPA•3/20/25, 9:18 PM

thats will be easier...

SSeekerdasbatatas I have a PR to get `vitest-pool-workers` to not crash with Workflows: https://gi...

K

kchro3•3/21/25, 8:49 PM

any updates on this? the agents SDK is also exporting workflows for some reason and now my tests are breaking again

AAslak Hellesoy Has anyone managed to get logs from workflows? When a workflow step fails, there...

M

Marco Aleixo•3/22/25, 8:48 PM

hey Aslak, curious if you made progress with sentry integration - I'm working to add sentry in my workflows as well - and we already struggled to instrument Queues...

A

ajay | dreamlit.ai•3/24/25, 3:43 PM

@Marco Aleixo @Aslak Hellesoy spent many hours on getting stack traces to show up in Sentry. Here's what finally worked:

A

ajay | dreamlit.ai•3/24/25, 3:44 PM

Z

zhawtof•3/24/25, 8:27 PM

Creating a workflow that is iterating through a list with pagination. The pagination operation works with a

next_cursor

next_cursor

next_cursor

next_cursor so that you know the next page to go and fetch. My question:

Can I capture the next_cursor in a let like below to reference in each subsequent step?

let next_cursor;
do {
  next_cursor = await step( ...call API and do stuff ...);
} while (next_cursor !== null)

let next_cursor;
do {
  next_cursor = await step( ...call API and do stuff ...);
} while (next_cursor !== null)

let next_cursor;
do {
  next_cursor = await step( ...call API and do stuff ...);
} while (next_cursor !== null)

let next_cursor;
do {
  next_cursor = await step( ...call API and do stuff ...);
} while (next_cursor !== null)

M

Matt Silverlock•3/25/25, 4:37 PM

FYI for those of you with longer-running Workflows: we've increased the maximum CPU limit for all Workers to 5 minutes (just change a couple of lines of config): https://developers.cloudflare.com/changelog/2025-03-25-higher-cpu-limits/

Cloudflare Docs

Run Workers for up to 5 minutes of CPU-time

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

M

Matt Silverlock•3/25/25, 4:37 PM

B

Boragorn•3/25/25, 9:03 PM

hi,

I sent a batch of 5,000 workflow executions, and for some reason, many of them are stuck in a "QUEUED" state. No failures, no errors --just hanging there in that state

B

Boragorn•3/25/25, 9:05 PM

btw -- I have the workers paid plan

J

jordanfinners•3/26/25, 9:02 PM

Are workflows down?

J

jordanfinners•3/26/25, 9:02 PM

I've been getting internal errors since 8pm

M

Matt Silverlock•3/26/25, 9:39 PM

Seeing Workflows recover / complete as of a couple of minutes ago.

M

Matt Silverlock•3/26/25, 9:42 PM

Note: This impacted Workflows that made/make external requests. Workflows that only call bindings or otherwise don’t call out to the Internet were unaffected.

J

jordanfinners•3/26/25, 9:42 PM

Thank you so much for the quick response and resolution

B

Bryan Chen•3/27/25, 6:46 AM

Is it possible for workflow to wait for some events? One of the step needs to trigger an external api to do some work that may take up to few minutes. a webhook callback will be received once the task is completed along with the task result. So I want to have a step to make a request, and resume / continue the workflow after a response is received or eventually have it timeout. I was thinking about serialize the state to db and restore them on callback and figured I am about to reimplement half of the workflow's functionality.

B

Bryan Chen•3/27/25, 6:50 AM

Can I use the pause/resume API achieve my goal? i.e. pause the workflow after the request is made, and resume after a response is received. Not sure if that's an intended way to use those API?

BBryan Chen Is it possible for workflow to wait for some events? One of the step needs to tr...

M

Matt Silverlock•3/27/25, 11:33 AM

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

K

Khafra•3/27/25, 4:23 PM

is

import { env } from 'cloudflare:workers'

import { env } from 'cloudflare:workers'

import { env } from 'cloudflare:workers'

import { env } from 'cloudflare:workers' populated in workflows? just wondering, can't really test this spot in my code

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

J

Jadugar_Jaggu•3/30/25, 7:36 AM

WOW Cloudflare Workers just leveled up from a beast to a TITAN

D

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

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

D

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

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

D

Deltachaos•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

Deltachaos•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

I am looping over a json array. each step does some api calls and changes the item inside the json.

Similar Threads

Similar Threads

Similar Threads