workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
Once a DO is created, it does not move.
/cdn-cgi/trace
, then seeing the colo fieldhello here. I have a weird behavior,
const response = await stub.fetch('https://durable-object/something')
return await handleResponse(response)
const response = await stub.fetch('https://durable-object/something')
return await handleResponse(response)
Just hit a problem where having Durable
yea........ what a sad realization :

Hi guys has anyone managed to get
Apologies, I should have been more clear
So I'm getting ready to publish
IttyDurable
(which extends DurableObject
)...
In order for test coverage to work (GH actions), I need to make sure the environment can see/accept DurableObject
, which I currently read from cloudflare:workers
, assuming a Wrangler setup. Any trick/tips on how to make sure that can be used in GH actions/test runners?...Kevin Whitley (@kevinrwhitley) on X
Is there a way to bind multiple workers
wrangler.toml
and re-exporting the DO in both index.ts
of the two workers, Cloudflare creates two seperate DO's with the worker name prefixed in front.
I can see how this is expected behaivour, but is there any way I can bind multiple workers into the same DO?...Limits · Cloudflare Workers docs
Hello, I am trying to use Websocket
Hey guys, seeing this error when adding
Cannot apply new-class migration to class AtlasWebsocket that is already depended on by existing Durable Objects [code: 10074]
I am adding this for the first time and I don't see it in use at all in console.
This is what I have in the migration ...since 2 days ago I'm getting a ton of
internal error
and Network connection lost.
errors when calling my durable objects. they don't have particularly high load and it happens to many different instances, not just one
there's no useful error to help me fix it unfortunately...WS debugging chat
Amazing, @Frederik — thanks for
@bun - okay, things are working, though
Hey all - I'm having quite a lot of
In this case you could also use
serializedAttachment
on that particular WebSocket, assuming you haven't used up all the space with other stuffclosing old websocket server instances without errors