Cloudflare Developers

CD

Cloudflare Developers

Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news

Join

I'm facing a lot of

I'm facing a lot of A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset. while seeing spikes on my file upload endpoint, and this is happening on something internal on my Workflows, and those errors seems to be not retriable, how fix this?...

Hi, is there a way to get the statuses

Hi, is there a way to get the statuses of multiple workflows in a single request? We have a number of workflows that we’d like to be able to get the statuses of, without making multiple parallel calls.

Are there any best practices for

Are there any best practices for implementing a workflow that is used for starting and stopping third party services? I was considering storing a lock in a durable object that states if the start workflow has already been executed you can only run the stop workflow but you still need to track the workflow instance id....

I see one of the workflows examples

I see one of the workflows examples shows waiting for a web hook event. How would you deal with the scenario of a web hook being received before the workflow begins waiting for it? Are events queued up in any way?

Now I'm running into this as well `(

Now I'm running into this as well (workflow.not_found) Provided Workflow does not exist in production. Anyone on the Cloudflare team know what could be happening? Seems a few other people have run into this....

workflow not found debugging 05/05

UI shows so: Following is my wranger.toml parts ``` name = "docpad-session-init" main = "src/index.ts"...
No description

😬 , i am running bullmq for now buts

😬 , i am running bullmq for now buts its failing, otherwise i have to scale that or run kafka until this is resolved I dont wanna use this until the issues are fixed otherwise i will end up having same issue after the migration...

I am not sure what has happened with

I am not sure what has happened with workflows product recently, but since yesterday, the product just doesn't work for me, i've had to stop everything, and now looking at alternative solutions. I can't trigger / pause / resume / terminate any workflows, l met with the error code 10001 as earlier. Over 3000 workflows failed yesterday with the exact same error This instance experienced an internal error which prevented it from running. If this is persistent, please contact support: https://cfl.re/3WgEyrH...

I might have identified a bug related to

I might have identified a bug related to waitForEvent. Here's the relevant code: ``` export class SimpleWorkflow extends WorkflowEntrypoint<...

Can someone help me with this?

Can someone help me with this?
No description

I'm experiencing some cases where new

I'm experiencing some cases where new workflow instances are being created and remain in the queued status forever

Workflow run in "waiting" state

I got something odd, where some of my workflow runs are suddenly in a "waiting" state, even though I didn't pause them or anything. I've checked and they're also not executing anything since I keep track of progress (even within steps) in a database. New workflow runs are running properly.

I haven't had any issues so far but also

I haven't had any issues so far but also haven't played with hibernation much so far 😅 ... but I want to know if my assumption is correct. Rules of workflows stating that you should not depend on state define solely outside of a step, and workflows can use outputs of steps across their execution. So... would somethint like this be OK?...

local dev not working

in this case, I think that you need to update the vitest-pool-workers package

So after further investigation, it turns

So after further investigation, it turns out any time the dev server reloads (any code change), every workflow instance disappears. This is really annoying. Is this expected? You can repro with the workflows starter template easily. npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflows-starter"...

I'm running into a somewhat frustrating

I'm running into a somewhat frustrating auth error when trying to trigger or list workflows via the cloudflare npm package …

Suddenly whenever my worker invokes my

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

could you get me your account id please

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

workflow create batch issues

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

Creating a workflow that is iterating

Creating a workflow that is iterating through a list with pagination. The pagination operation works with a 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? ```ts let next_cursor;...