They're not supposed to, the workflow team as in that msg wants to fix it, but they currently all do
They're not supposed to, the workflow team as in that msg wants to fix it, but they currently all do
Csame as above ^, as said in the thread "for now I'd just look at the workflows page to see how your instances are doing."
KHi, 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
but I'm wondering if there's anything better?
I can think of some ideas like
but I'm wondering if there's anything better?
Kmaybe a DurableObject is better in this case
MCall
step.sleep within the step when you get a rate limiting error? with the argument as the future Date?Kit never even crossed my mind to have nested steps lol
Kthis changes everything
MWorkflows: it's just code 
AI 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.
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.
MTimeout is per step... with
20160 total retries before it will terminally fail. 2 minute is not the total time for all retries.MAnd by "stuck" - have you attempted to call
.stop on the instance? What error do you get (if any) when you call terminate in the dash?
Awouldn'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
T
AYeah but only running the workers with the same command
wrangler -c ... -c ... locally
Kis it possible to handle these exceptions so that they don't flood our metrics dashboard?
AI 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
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
HWhat do the steps in the loop return?
ARight, we should have expected retry functionality there correct? It appears that it was in that stuck in that
Even after I terminated the instance, while the workflow run changed the status to
Thank you for your help!
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, the step status still says Running. See screenshot. Perhaps I've misconfigured something? Thank you for your help!
Afixed it! I make the loop part of a bigger step and get and set base don that!
OI'm getting an error fetching a file from R2 within my workflow
HI’m guessing that’s probably because an R2 file is not serializable
Jdo you know where can i found a example code with impaiting working?
Jthats will be easier...
Kany updates on this? the agents SDK is also exporting workflows for some reason and now my tests are breaking again 
Mhey 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@Marco Aleixo @Aslak Hellesoy spent many hours on getting stack traces to show up in Sentry. Here's what finally worked:
A
ZCreating a workflow that is iterating through a list with pagination. The pagination operation works with a
Can I capture the next_cursor in a let like below to reference in each subsequent step?
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?
MFYI 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/
Bhi,
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
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
Bbtw -- I have the workers paid plan
JAre workflows down?
JI've been getting internal errors since 8pm
MSeeing Workflows recover / complete as of a couple of minutes ago.
MNote: This impacted Workflows that made/make external requests. Workflows that only call bindings or otherwise don’t call out to the Internet were unaffected.
JThank you so much for the quick response and resolution 
BIs 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.
BCan 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?
MWe’re working on a waitForEvent API that should land very soon.
Kis
import { env } from 'cloudflare:workers' populated in workflows? just wondering, can't really test this spot in my code
JWOW Cloudflare Workers just leveled up from a beast to a TITAN
Dis it possible to see logs created by "console.log" in the steps somewhere?
Dand i dont see any information about what the limits for workflows are in the free tier?
Dand is it possible to use workflows with python or rust?
MCloudflare Docs
Store, filter, and analyze log data emitted from Cloudflare Workers.
MCloudflare Docs
Limits that apply to authoring, deploying, and running Workflows are detailed below.
Dalso for console.logs from workflows?
MYes.
GI forgot this happened, thanks! That helps with a large file I have to process and was difficult to split among workers