Anyone else having issues deploying a workflows worker? Even when logged into wrangler with a user w

7

7777777•5/30/25, 6:08 PM

Maybe I missed a step, but do I need to manually setup a Service binding for my workflow? I have a worker which accepts fetch requests, and the same worker defines 3 different workflows. Locally everything seems to run fine via the toml file. When I deploy I can see the workflow deploys happening, however when I goto

<MY_WORKER>/production/settings#bindings

<MY_WORKER>/production/settings#bindings

<MY_WORKER>/production/settings#bindings

<MY_WORKER>/production/settings#bindings then workflows are not shown. I was going to add them manually as a service, but am I going to have to do this for every deployment?

Kkacper Hey, I'm implementing some workflow ```typescript await step.do("process-events...

7

7777777•5/30/25, 6:12 PM

you could use kv to store state and track which

events

events

events

events and

i

i have been inserted already, so that way on retry you would just check the kv for where to start. - depending on db you might also want to do all the inserts as a batch after

events.length

events.length

events.length

events.length has been processed, which would reduce the number of kv writes to track

i

i.

JJustin Anyone else having issues deploying a workflows worker? Even when logged into wr...

T

Tait•5/30/25, 6:13 PM

Yah we have a discussion going about this in the #wrangler channel

T

Tait•5/30/25, 6:13 PM

seems to just happen with workflow deployments (not regular workers)

TTait Yah we have a discussion going about this in the #wrangler channel

J

JustinOP•5/30/25, 6:16 PM

Thanks! Will follow along there..

M

mochachai•5/30/25, 6:17 PM

I have a lot of weird stuff going on. My prod workflow is suddenly not bound anymore to prod DB but the binding seems to point at the dev DB? really weird

T

Tait•5/30/25, 6:17 PM

We I say "we", no one from cloudflare has weighed in just yet. Hoping to hear something soon. Not sure if/how to escalate

JJustin Anyone else having issues deploying a workflows worker? Even when logged into wr...

A

ac•5/30/25, 6:19 PM

Yes, I'm having the same issue right now. Must be a Cloudflare problem

J

James•5/30/25, 6:44 PM

I've escalated, thanks folks. Hopefully we'll see a resolution shortly.

W

Walshy•5/30/25, 6:51 PM

https://www.cloudflarestatus.com/incidents/6xdvg9z3qnjy

Issues Deploying Workflows

W

Walshy•5/30/25, 7:47 PM

You should be able to deploy now :)

Sorry for the issue!

A

ac•5/30/25, 7:54 PM

Looks like it's working for me now

7

7777777•5/31/25, 12:18 AM

when I call

await env.MY_WORKFLOW.createBatch(listOfInstances);

await env.MY_WORKFLOW.createBatch(listOfInstances);

await env.MY_WORKFLOW.createBatch(listOfInstances);

await env.MY_WORKFLOW.createBatch(listOfInstances); it's returning

[{"fetcher":{}}]

[{"fetcher":{}}]

[{"fetcher":{}}]

[{"fetcher":{}}] instead of WorkflowInstances?

7

7777777•5/31/25, 1:38 AM

The workflow status

errored

errored

errored

errored is both a terminal and transient state. There should be a separate state signalling the workflow has exhausted all retries.

Hharisvsulaiman I lost all my bindings to the workfkow

M

Matt Silverlock•5/31/25, 10:43 AM

Can you give us more info? When you deploy, what happens?

Show the output of wrangler - does it pick up the bindings?

Hharisvsulaiman Yes @Matt

M

Matt Silverlock•5/31/25, 10:48 AM

OK, so the bindings are there. What happens? I need you to show the errors / describe the issue in more detail otherwise I can’t help you.

M

Matt Silverlock•5/31/25, 10:49 AM

Paste it here please.

M

Matt Silverlock•5/31/25, 10:49 AM

Help me help you.

M

Matt Silverlock•5/31/25, 10:49 AM

Paste YOUR errors.

77777777 when I call `await env.MY_WORKFLOW.createBatch(listOfInstances);` it's returning...

7

7777777•5/31/25, 1:05 PM

I should add this only happens in prod, when running locally the call returns a a Promise with an array of WorkflowInstance.

F

fforres•5/31/25, 9:49 PM

@7777777 Did this started happening recnetly for you?
I started seeing this for a deployment on prod as well.

7

7777777•5/31/25, 9:50 PM

Recent for me as of the wrangler deploy issue

F

fforres•5/31/25, 9:51 PM

@7777777 A specific wrangler deploy issue?
Just updated to 4.18.0 and wondering if this might've been it

WWalshy https://www.cloudflarestatus.com/incidents/6xdvg9z3qnjy

7

7777777•5/31/25, 9:52 PM

I noticed it after this issue was resolved.

F

fforres•5/31/25, 9:55 PM

Gotcha. Yeah, seeing that now also. Had a small helper to split workstreams into batched workflow executions.
And then polling to see if the workflow finished.
But it's started failing

Glad I'm not the only one. ... sucks that it's happening

F

fforres•5/31/25, 9:55 PM

cc @Matt @Luís Duarte

JIC / FYI / PSA

F

fforres•5/31/25, 10:37 PM

JIC someone else finds this.

I was using the returned worflowInstances IDs to do poll until workflows were done.
That flow is broken, but you can still manually set a worfklow ID, then fetch the workflows instances manually and do stuff with that instead

J

johtso•6/1/25, 7:42 AM

This is kind of concerning for something that's supposed to be GA production ready..

D

darkpool•6/1/25, 5:46 PM

I can't even get the example working. It queues up then instantly fails with an internal error.

Describing latest instance:
Workflow Name:  workflows-starter
Instance Id:    c369baf1-8d53-4f35-be6b-47c037ff0cb0
Version Id:     e2306101-587c-46a1-9451-14a9bef15921
Status:         ❌ Errored
Trigger:        🌎 API
Queued:         6/1/2025, 12:40:50 PM
Success:        ❌ No
Start:          6/1/2025, 12:40:50 PM
End:            6/1/2025, 12:40:52 PM
Duration:       2 seconds
Error:          Error: internal error; reference = la5trq1a8b4ie9ka6vclinv6
Steps:

Describing latest instance:
Workflow Name:  workflows-starter
Instance Id:    c369baf1-8d53-4f35-be6b-47c037ff0cb0
Version Id:     e2306101-587c-46a1-9451-14a9bef15921
Status:         ❌ Errored
Trigger:        🌎 API
Queued:         6/1/2025, 12:40:50 PM
Success:        ❌ No
Start:          6/1/2025, 12:40:50 PM
End:            6/1/2025, 12:40:52 PM
Duration:       2 seconds
Error:          Error: internal error; reference = la5trq1a8b4ie9ka6vclinv6
Steps:

Describing latest instance:
Workflow Name:  workflows-starter
Instance Id:    c369baf1-8d53-4f35-be6b-47c037ff0cb0
Version Id:     e2306101-587c-46a1-9451-14a9bef15921
Status:         ❌ Errored
Trigger:        🌎 API
Queued:         6/1/2025, 12:40:50 PM
Success:        ❌ No
Start:          6/1/2025, 12:40:50 PM
End:            6/1/2025, 12:40:52 PM
Duration:       2 seconds
Error:          Error: internal error; reference = la5trq1a8b4ie9ka6vclinv6
Steps:

Describing latest instance:
Workflow Name:  workflows-starter
Instance Id:    c369baf1-8d53-4f35-be6b-47c037ff0cb0
Version Id:     e2306101-587c-46a1-9451-14a9bef15921
Status:         ❌ Errored
Trigger:        🌎 API
Queued:         6/1/2025, 12:40:50 PM
Success:        ❌ No
Start:          6/1/2025, 12:40:50 PM
End:            6/1/2025, 12:40:52 PM
Duration:       2 seconds
Error:          Error: internal error; reference = la5trq1a8b4ie9ka6vclinv6
Steps:

Ddarkpool I can't even get the [example](https://developers.cloudflare.com/workflows/get-s...

M

Matt Silverlock•6/1/25, 8:43 PM

Can you share your account ID? Are you seeing this repeat? (attempting to reproduce but can't)

M

Matt Silverlock•6/1/25, 8:45 PM

(The second step errors as expected)