I haven't done any of this myself but I believe that RPC has the concept of a "session". I don't thi

I haven't done any of this myself but I believe that RPC has the concept of a "session". I don't think you pay for requests during a "session". I also believe that sessions timeout though so I'm guessing you have to sense when that happens and create a new session.

LLarry I haven't done any of this myself but I believe that RPC has the concept of a "s...

1984 Ford Laser•10/10/25, 12:04 AM

The session you talk about would be related to stubs and RpcTarget right? I don't like having to think about whether a new stub needs to be made and stuff. Currently, DO to DO RPC requires at least 2 requests per RPC call. If I use websockets, I make one request to connect, then I can send 20 messages for the price of 1

11984 Ford Laser The session you talk about would be related to stubs and RpcTarget right? I don'...

LarryOP•10/10/25, 12:18 AM

Fair enough. I still use fetch between DOs. Someday I'll start playing with RPC, RpcTarget, etc.

Peps•10/10/25, 12:55 AM

hm?

vcc•10/10/25, 2:26 AM

Did workers release a new version yesterday? My service got more errors than last full week.

11984 Ford Laser The session you talk about would be related to stubs and RpcTarget right? I don'...

lambrospetrou•10/10/25, 6:36 AM

Currently, DO to DO RPC requires at least 2 requests per RPC call

What do you mean 2 requests per RPC call? There should only be one round trip for a normal RPC call.

Llambrospetrou > Currently, DO to DO RPC requires at least 2 requests per RPC call What do you ...

1984 Ford Laser•10/10/25, 7:46 AM

Sorry I was including the call to the Worker as well

blindChicken•10/10/25, 1:35 PM

I'm seeing some weird behavior

happening in my Durable Objects "Live" logs. I'm seeing requests for an unrelated worker, that is a worker in a different project? It's a project that gets a lot of traffic compared to others, so I'm note sure if it is showing the traffic for all my workers or not. But there is a problem!

Alex Dahl•10/11/25, 7:03 PM

Has anyone else seen issues with ios 26 websockets and connecting to durable objects? I encountered this issue with one of my users. I think it might be an Apple issue, but I have only seen it once so far. They were using private relay

Apple forum thread: https://discussions.apple.com/thread/256142477?sortBy=rank

Lulu•10/12/25, 6:00 AM

I'm a little confused about how PITR works. The API says

getCurrentBookmark()

getCurrentBookmark()

and

getBookmarkForTime()

getBookmarkForTime()

return a

Promise<string>

Promise<string>

, but the example right below it shows it being used without a promise:

let now = new Date();
// restore to 2 days ago
let bookmark = ctx.storage.getBookmarkForTime(now - 2);
ctx.storage.onNextSessionRestoreBookmark(bookmark);

let now = new Date();
// restore to 2 days ago
let bookmark = ctx.storage.getBookmarkForTime(now - 2);
ctx.storage.onNextSessionRestoreBookmark(bookmark);

Assuming it returns a promise, how can I guarantee the bookmark I get is accurate?

let bookmark = await getCurrentBookmark();
// stuff may happen here while it is awaiting
this.sql.exec(/* omitted */);

let bookmark = await getCurrentBookmark();
// stuff may happen here while it is awaiting
this.sql.exec(/* omitted */);

geg•10/12/25, 6:31 AM

I can't help but read it as pain in the rear

Lulu•10/12/25, 6:34 AM

Looking up the workerd codebase, I found this:

// Get a bookmark for the current state of the database. Note that since this is async, the
// bookmark will include any writes in the current atomic batch, including writes that are
// performed after this call begins. It could also include concurrent writes that haven't happened
// yet, unless blockConcurrencyWhile() is used to prevent them.
kj::Promise<kj::String> getCurrentBookmark();

// Get a bookmark for the current state of the database. Note that since this is async, the
// bookmark will include any writes in the current atomic batch, including writes that are
// performed after this call begins. It could also include concurrent writes that haven't happened
// yet, unless blockConcurrencyWhile() is used to prevent them.
kj::Promise<kj::String> getCurrentBookmark();

But it is hard to tell what "concurrent writes that haven't happened yet" means. Is it saying after the callback returns, the bookmark will be accurate?

Harrison Lo•10/12/25, 6:50 PM

I wonder if each Durable Object will come with its own R2 binding too in the future

LLulu I'm a little confused about how [PITR](https://developers.cloudflare.com/durable...

lambrospetrou•10/13/25, 9:41 AM

Configures the Durable Object so that the next time it restarts, it should restore its storage to exactly match what the storage contained at the given bookmark. After calling this, the application should typically invoke ctx.abort() to restart the Durable Object, thus completing the point-in-time recovery.

As the docs say,

onNextSessionRestoreBookmark

onNextSessionRestoreBookmark

works on the next restart, so you need to kill the DO for the restore to happen.

As mentioned multiple times, I suggest you always

await

await

explicitly any async operation. The example there probably depends on implicit transactions, but just await in your code to be able to reason about things.

ALECKS•10/13/25, 1:33 PM

If I want to do a "fire and forget" on a DO method, is there any functional difference between:

ctx.waitUntil(doSomething())

ctx.waitUntil(doSomething())

and

setting an alarm in, say 100ms, return, then let the DO
```
doSomething()
```
```
doSomething()
```
as a result of the alarm
?

Llambrospetrou > Configures the Durable Object so that the next time it restarts, it should res...

Lulu•10/13/25, 6:33 PM

Thanks. Just to be clear, you are saying by awaiting the bookmark in the example below, and then restoring the database to that bookmark, the transaction that happened after is guaranteed to be absent from the restored version?

let bookmark = await getCurrentBookmark();
// stuff may happen here while it is awaiting
this.sql.exec(/* omitted */);

let bookmark = await getCurrentBookmark();
// stuff may happen here while it is awaiting
this.sql.exec(/* omitted */);

LLulu Thanks. Just to be clear, you are saying by awaiting the bookmark in the exampl...

lambrospetrou•10/13/25, 7:53 PM

If you await, then the comment is wrong, since nothing will happen until the promise to get the bookmark resolves.
Any write happening after you got your bookmark is not included in the version pointed by that bookmark.

Earl•10/13/25, 8:20 PM

When binding to a DO in another worker while using enviroments using { "environment": "staging", "script_name": "api", ... } does not work
error: Cannot create binding for class in script 'api' that does not exist. [code: 10061]

The following binding does work: { "script_name": "api-staging", ... }

Which is expected - but why can't I use the environment property alternatively? What else is its use?

ALECKS•10/13/25, 9:03 PM

The docs say that DurableObject KV storage is Synchronous: https://developers.cloudflare.com/durable-objects/api/sqlite-storage-api/#synchronous-kv-api
However, the generated typescript types show that

ctx.storage.get()

ctx.storage.get()

returns a Promise.

Is this a bug or am I missing something?

AALECKS The docs say that DurableObject KV storage is Synchronous: https://developers.cl...

Isaac McFadyen•10/13/25, 9:09 PM

That's for the SQLite KV API, are you looking at the types for the original KV storage in DOs perhaps?

AALECKS The docs say that DurableObject KV storage is Synchronous: https://developers.cl...

1984 Ford Laser•10/13/25, 9:12 PM

ctx.storage.kv.get()

ctx.storage.kv.get()

is the sync API (in SQLite DOs)

1984 Ford Laser•10/13/25, 9:12 PM

ctx.storage.get()

ctx.storage.get()

is the old async API

IIsaac McFadyen That's for the SQLite KV API, are you looking at the types for the original KV s...

ALECKS•10/13/25, 9:13 PM

Ah thank you, missed that

.kv

.kv

BBrayden am I allowed to say "this week" again?

sebws•10/14/25, 1:43 AM

did this happen?

EEarl When binding to a DO in another worker while using enviroments using { "environm...

lambrospetrou•10/14/25, 6:53 AM

Your worker names are different for each environment right? If you remove the

environment

environment

and keep the

script_name

script_name

with the correct worker name does it work? The error says there isn't any worker with the name

api

api

which is correct, since you say the worker is

api-staging

api-staging

.

Environments are not a semantic thing all things understand, I personally see it mostly as a wrangler thing to group your configuration, but then the resources are identified by their own IDs/names.

Llambrospetrou Your worker names are different for each environment right? If you remove the `e...

Earl•10/14/25, 9:11 AM

Since wrangler automatically suffixes the env name to the worker name it does make sense. What doesn't make sense to me is that the DO binding configuration has an environment property:
https://developers.cloudflare.com/workers/wrangler/configuration/#durable-objects
What does it do?

Cloudflare Docs

Configuration

Use a configuration file to customize the development and deployment setup for your Worker project and other Developer Platform products.

EEarl Since wrangler automatically suffixes the env name to the worker name it does ma...

lambrospetrou•10/14/25, 9:41 AM

Not sure, but my guess would be it's from the deprecated "service environments" thing that was tried out a few years ago.

BBrayden Durable Objects will have a built in Studio in the dashboard next week if this f...

christianklotz•10/14/25, 9:51 AM

Is this GA? My Durable Objects dashboard looks like it still uses the previous design

Llambrospetrou Not sure, but my guess would be it's from the deprecated "service environments" ...

Earl•10/14/25, 10:01 AM

Ah alright, thanks!

icemelt_melt•10/14/25, 11:14 AM

I want to know will ever Durable Objects or D1 come to Dubai region?

Nick•10/14/25, 12:57 PM

Has anyone managed to successfully wrap durable objects classes?

I am looking at how sentry does it:
https://github.com/getsentry/sentry-javascript/blob/develop/packages/cloudflare/src/durableobject.ts
And it's really rather complex!

We want to wrap all the methods on our durable object in an AsyncLocalStorage context but keep getting errors with the wrong

this

this

being bound, or shared IO stuff, or private member access. We tried doing it with a proxy, and then copying the sentry approach. Both got close but had some error conditions like

Cannot perform I/O on behalf of a different Durable Object

Cannot perform I/O on behalf of a different Durable Object

Cannot read private member #_name from an object whose class did not declare it

Cannot read private member #_name from an object whose class did not declare it

GitHub

sentry-javascript/packages/cloudflare/src/durableobject.ts at devel...

Official Sentry SDKs for JavaScript. Contribute to getsentry/sentry-javascript development by creating an account on GitHub.

Cchristianklotz Is this GA? My Durable Objects dashboard looks like it still uses the previous d...

Brayden•10/14/25, 8:28 PM

....this week

promise!

Lulu•10/14/25, 10:23 PM

are there plans to add more jurisdictions for Durable Objects?

Earl•10/14/25, 10:40 PM

I have a DO that is defined in worker-a but used in worker-b as well. I generate types for worker-b like this:
wrangler --cwd worker-b types -c wrangler.jsonc -c ../worker-a/wrangler.jsonc

This works and I get the right types when accessing the DO in worker-b.

The problem is that when I run tsc on worker-b I get type errors because the worker-configuration.d.ts imports all of worker-a (and not only the DO class):
interface Env {
do: DurableObjectNamespace<import("../worker-a/src/index").DO>;
}

worker-a uses env variables in code unrelated to the DO that are not available in worker-b which lead to the type error.

What is the recommended architecture for shared DOs? I was thinking of putting them in a separate worker that only holds the DOs and is not actually callable. But I'm not sure if that's how it's meant to be done.

JonathanR•10/15/25, 3:54 PM

In the last few weeks we've started to see random

RangeError: Invalid typed array length:

RangeError: Invalid typed array length:

in durable objects. The lengths reported are all well within what should be a valid range. It seems like others are having similar issue as well, although those have to do with Prisma, which we are not using.

Earl•10/15/25, 9:19 PM

When calling a DO of another worker, will the DO have the env of the calling working or of the worker that hosts the DO?

EEarl When calling a DO of another worker, will the DO have the env of the calling wor...

geg•10/15/25, 9:28 PM

host

EEarl I have a DO that is defined in worker-a but used in worker-b as well. I generate...

Earl•10/15/25, 10:29 PM

I've opened a bug regarding this (with a reproduction):
https://github.com/cloudflare/workers-sdk/issues/10993

GitHub

Type error using other worker's durable object when workers' Env di...

What versions & operating system are you using? System: OS: Windows 11 10.0.26100 CPU: (12) x64 AMD Ryzen 5 9600X 6-Core Processor Memory: 15.82 GB / 31.11 GB Binaries: Node: 24.7.0 - C:\Users...