Real-time updates for Cloudflare Workflows using Durable Objects: - create Workflow with UUID - create Durable Object (same UUID) - create update method - browser opens socket connection to Durable Object Each Workflow step calls the `update` method of the DO

worth flipping one assumption: don’t call update on every step. Push only human-meaningful checkpoints (started / waiting / failed / done). Otherwise the progress UI becomes a log firehose and the DO is just an expensive console.log.

Yes absolutely. You can imagine the stereotypical path is one update for step, but obviously only for the ones that make sense for th euser

euser is the end user or user from EU? different users:))

Cloudflare always rocking

This pattern is super clean. Using DOs as the glue for real-time state updates makes the whole workflow feel much more responsive for the end user.

We thought so!

can you stop to do cool stuff ?

What do you mean?

I meant the opposite: stop making cool stuff, I cannot keep up. @HoldsUpApp runs on Workers, D1, Workflows and one container, and this is the piece I was missing for live pipeline progress.

the shared uuid makes this click for me. every step can report through the same durable object, so the browser gets one live view of the run.

can anyone help me solve this problem, I can't visit any website with cf.

Sharing a UUID between the Workflow and the Durable Object is a neat trick — it turns "where do I put the progress state" into a naming convention instead of a service. The interesting question is what happens on retry: if a step re-runs, does the DO get the update twice, and is `update` idempotent by design or by discipline?

The basic implementation would see the same update twice. BUT that shouldn't matter if it's the same status right? The user wouldn't know the difference

the socket should be disposable. persist a monotonic event cursor in the Durable Object and replay missed workflow updates after reconnect. otherwise every laptop sleep turns a correct workflow into a lying progress UI.

I think that's one piece we didn't cover in the short tweet. The concept of saving the latest status to key/value store in DO. Then, share that status immediately on new connections. That what you mean?

Cool

I love the video format. It’s pleasant to watch it on the phone without having to rotate

oh what