Hey folks, we continue to see error logs for our workflow that just say "run". if I filter by reques

Hey folks, we continue to see error logs for our workflow that just say "run". if I filter by request ID, I can see that the workflow successfully executed other steps, so I don't know where the "run" error log is coming from.

Kkchro3 Hey folks, we continue to see error logs for our workflow that just say "run". i...

Chaika•3/15/25, 7:59 PM

it's just how the workflow invocations show

Chaika•3/15/25, 8:00 PM

https://discord.com/channels/595317990191398933/1303411588929294358/1303488051917492318

kchro3OP•3/15/25, 8:00 PM

Are they supposed to be shown as errors?

Chaika•3/15/25, 8:01 PM

They're not supposed to, the workflow team as in that msg wants to fix it, but they currently all do

Rrodrigo anyone figured out what causes this error? We are still seeing this regularly on...

Chaika•3/15/25, 8:03 PM

same as above ^, as said in the thread "for now I'd just look at the workflows page to see how your instances are doing."

Khafra•3/15/25, 11:55 PM

Hi, is it possible to set the retry steps after a workflow fails? For example one of my workflow steps calls a third party api where I don't know the ratelimits. I want to fail the step if I'm ratelimited, but then retry at a specific date (the api gives us this date if we're ratelimited).

I can think of some ideas like

for (const param of params) {
  while (true) {
    const response = await step.do('<random name>', { /* options to not retry */ }, ...)

    if (response.status === 429) {
      await step.sleep('ratelimit expires', Number(response.headers.get('X-RateLimit-Reset')) * 1000)
    } else {
      break
    }
  }
}

for (const param of params) {
  while (true) {
    const response = await step.do('<random name>', { /* options to not retry */ }, ...)

    if (response.status === 429) {
      await step.sleep('ratelimit expires', Number(response.headers.get('X-RateLimit-Reset')) * 1000)
    } else {
      break
    }
  }
}

but I'm wondering if there's anything better?

Khafra•3/16/25, 12:03 AM

maybe a DurableObject is better in this case

KKhafra Hi, is it possible to set the retry steps *after* a workflow fails? For example ...

Matt Silverlock•3/16/25, 12:55 AM

Call

step.sleep

step.sleep

within the step when you get a rate limiting error? with the argument as the future Date?

Khafra•3/16/25, 12:55 AM

it never even crossed my mind to have nested steps lol

Khafra•3/16/25, 12:59 AM

this changes everything

Matt Silverlock•3/16/25, 1:07 AM

Workflows: it's just code

ajay | dreamlit.ai•3/17/25, 2:30 PM

I have a workflow run that appears to be stuck in "RUNNING" state. Here's what the dashboard shows for the run.

Any idea on what might be up? As you can see there's both a timeout and retry for this step, both of which appear to be ignored.

Aajay | dreamlit.ai I have a workflow run that appears to be stuck in "RUNNING" state. Here's what t...

Matt Silverlock•3/17/25, 8:42 PM

Timeout is per step... with

total retries before it will terminally fail.

2 minute

2 minute

is not the total time for all retries.

Aajay | dreamlit.ai I have a workflow run that appears to be stuck in "RUNNING" state. Here's what t...

Matt Silverlock•3/17/25, 8:50 PM

And by "stuck" - have you attempted to call

.stop

.stop

on the instance? What error do you get (if any) when you call

terminate

terminate

in the dash?

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

ajgeiss0702•3/17/25, 10:24 PM

wouldn't the dashboard show if there were other retries though? it looked like that one step's first try had been running for at least an hour based on that timestamp

Txantonnikole•3/18/25, 1:17 AM

MMurder Chicken Were you ever able to get this to work as-documented?

alex (he/him)•3/18/25, 6:37 AM

Yeah but only running the workers with the same command

wrangler -c ... -c ...

wrangler -c ... -c ...

locally

CChaika They're not supposed to, the workflow team as in that msg wants to fix it, but t...

kchro3OP•3/18/25, 4:15 PM

is it possible to handle these exceptions so that they don't flood our metrics dashboard?

Advany•3/19/25, 1:03 PM

I am looping over a json array. each step does some api calls and changes the item inside the json. But somehow the steps are overwriting each other sometimes and I loose progress from previous steps.

I get the json using a step and then create a loop to go over the array inside jte json and for each item I call the step again.

How can I prevent steps from overriding each other

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

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

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

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

, the step status still says

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?

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

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

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

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

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

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

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

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

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

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

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

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:

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

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

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)

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

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

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

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

btw -- I have the workers paid plan

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

Are workflows down?

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

I've been getting internal errors since 8pm

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

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

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.

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

Thank you so much for the quick response and resolution

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.

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

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

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

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

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