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

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

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

Right, we should have expected retry

Right, we should have expected retry functionality there correct? It appears that it was in that stuck in that 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!...
No description

If I try and use cross-script calls like

If I try and use cross-script calls like in the documentation... WORKER A wrangler.toml ``` [[workflows]]...

I have workflow working locally and I

I have workflow working locally and I see the binding working on remote, but when I try to trigger it via worker I am seeing TypeError: Cannot read properties of undefined (reading 'create') c.env.COVE_WORKFLOW_VIDEO.create({ I think it is saying that the actual workflow is not bound. below is the hono api call that triggers it...

It might be naive question but i am

It might be naive question but i am having hard time seeing console output. i have a workflow that makes call to AWS lambda and for some reasons lambda is returning error, to debug, i have added logs, which do not appear in workflow dashboard, and i see nothing in wrangler tail. is there any guide or recommendation on how to debug the workflow?

Hey, i'm noticing a lot of errors with

Hey, i'm noticing a lot of errors with the messages thrown by step.do. and workflows not loading on cloudflare since yesterday, this wasn't happening before A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset is it just me or is anyone else having the same issue? 🤔...

Seeing this error:

Seeing this error: ``` { "$workers": {...

Hi all, just started using workflows.

Hi all, just started using workflows. Overall, extremely rad. Something baffling me is the __LOCAL_DEV_STEP_OUTPUTS and what the equivalent would be from a deployed workflow? obvs I can trial-and-error this, but I wanted to ID documentation on this vs. "production" outputs 😄...

Gotcha - ok, thank you! I'll do some

Gotcha - ok, thank you! I'll do some experimentation later today to see if I can get it to work with another worker w/ service bindings - and if not, probably another worker doing a normal fetch().

can someone confirms AsyncLocalStorage

can someone confirms AsyncLocalStorage will not behave as expected in a step fn unless the callback is defined inline ? ```ts async run(event: WorkflowEvent<Params>, step: WorkflowStep) { await context.run({ id: "124" }, async () => { // loadFile will get undefined when calling content.getStore() ...

Hey!

Hey! I'm trying to use Workflows within an existing Workers project. The project is using vite to build a remix app. But I'm getting this error if I try to add a workflows configuration into wrangler.jsonc: ```Worker "workflows:workflow"'s binding "USER_WORKFLOW" refers to service "core:user:" with a named entrypoint "ExcelImportWorkflow", but "core:user:" has no such named entrypoint....

Workers RPC — Lifecycle · Cloudflare Wor...

Hi all! I'm running into the following error when using Workflows: An RPC stub was not disposed properly. You must call dispose() on all stubs in order to let the other side know that you are no longer using them. You cannot rely on the garbage collector for this because it may take arbitrarily long before actually collecting unreachable objects. As a shortcut, calling dispose() on the result of an RPC call disposes all stubs within it. I see that step.do expects to return Rpc.Serializable<unknown>, so I did a little bit of reading about the RPC lifecycle here and found that in the context of Worker Service Bindings, you should either use the experimental using syntax, or explicitly call object[Symbol.dispose](). ...

Hi folks - having some trouble with

Hi folks - having some trouble with throwing errors inside a workflow. First, it seems throwing a NonRetryableError, is retried as many times as specified Second, I can't seem to find out where the throw error messages are being returned in the workflow status. The docs seem to say const wf = await MY_WORKFLOW.get(id) and then await wf.status() should return errors, but they are always empty....

is `npx wrangler types` supposed to work

is npx wrangler types supposed to work for workflows? wrangler.toml: services = [{ binding = "WORKFLOW_PROCESS_TRANSACTIONS", service = "money" }] wrangler version: wrangler 3.107.3 generated interface, WORKFLOW_PROCESS_TRANSACTIONS should be Workflow? ```...
Next