> Configures the Durable Object so that the next time it restarts, it should restore its storage to

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:

and
setting an alarm in, say 100ms, return, then let the DO 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...

lambrospetrouOP•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 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

is the sync API (in SQLite DOs)

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

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

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

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

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

environment

environment

and keep the 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 .

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

lambrospetrouOP•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

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

Silvan•10/16/25, 2:11 PM

the outerbase guys finally cooked

Silvan•10/16/25, 2:11 PM

(again)

gruntlord6•10/16/25, 2:33 PM

is it showing up yet for anyone? I do not see Data Studio in the dash

Larry•10/16/25, 2:43 PM

Huge congrats to Brayden and team on shipping DO Data Studio!

gruntlord6•10/16/25, 2:43 PM

I guess maybe it hasn't rolled out to my account yet or something, I'll have to try later. I am hyped to look at it though

Ggruntlord6 I guess maybe it hasn't rolled out to my account yet or something, I'll have to ...

boop•10/16/25, 2:44 PM

I refreshed a couple of times and it's now showing up

Bboop I refreshed a couple of times and it's now showing up

gruntlord6•10/16/25, 2:44 PM

so did I, but I tried when you said that and it's there now haha

gruntlord6•10/16/25, 2:46 PM

This is sick! I was hoping it would list your durable objects but this is 100% an improvement over having to install the outerbase package

gruntlord6•10/16/25, 2:47 PM

the bulk dropping of tables would be a nice thing to include though

Ggruntlord6 so did I, but I tried when you said that and it's there now haha

lambrospetrouOP•10/16/25, 2:47 PM

It should be open to everyone now, so refresh your dashboards if you don't see it

Llambrospetrou It should be open to everyone now, so refresh your dashboards if you don't see i...

gruntlord6•10/16/25, 2:49 PM

any chance you guys are looking at adding the bulk table dropping like the outerbase client had? or at least a way to not have to put in every table name when dropping multiple independently?

Brayden•10/16/25, 2:55 PM

told you guys it'd be here "next week"

hope you all enjoy it!!

Burrito•10/16/25, 3:07 PM

Is there a way to limit data studio to read only operations?

Burrito•10/16/25, 3:22 PM

It would also be nice to have better FTS support, currently they just show as

[object Object]

[object Object]

mvgrim•10/16/25, 3:26 PM

Also, seems like the Data Studio doesn't expose KV store data that is backed by the SQLite backend. Would be good to have an ability to query that data. I have some durable objects that use the new SQLite backing, but use the KV store API for its simplicity. I know those drop into a different table/DB in the SQLite store, but it's not exposed in Data Studio.

BBurrito It would also be nice to have better FTS support, currently they just show as `[...

Visal .In•10/16/25, 5:22 PM

Will work on it.

VVisal .In Will work on it. 🙂

Peps•10/16/25, 9:44 PM

Hey

If you're an Cloudflare employee, any chance you could do the

/cfrole

/cfrole

command to get the official employee role? It'll make it more clear you're part of the team

Xxormask I'm sure this is a commonly asked question, but what is my best solution for loc...

Larry•10/16/25, 10:27 PM

I just released which builds on vitest integration. See: https://lumenize.com/docs/testing/usage#basic-usage. Example:

Let me know what you think or if you have any questions.

Usage | Lumenize

Doc-testing – Why do these examples look like tests?

LLarry I just released `@lumenize/testing` which builds on `cloudflare:test` vitest int...

1984 Ford Laser•10/16/25, 10:30 PM

Glad to see the CORS support here! That was something I had just run into with so this is a prefect time for the release. Will definitely take a look

11984 Ford Laser Glad to see the CORS support here! That was something I had just run into with `...

Larry•10/16/25, 10:38 PM

You can use my package with my advanced CORS supporting . I recommend the whitelist approach. See: https://lumenize.com/docs/utils/route-do-request#cors-support

However, the latest version of which is what shows using in the docs has all or nothing CORS support. The third parameter is a config object and will allow all cross origins.

Request Routing | Lumenize

Route HTTP and WebSocket requests to Durable Objects with authentication hooks

LLarry You can use my `json-rpc-mixin` package with my advanced CORS supporting `routeD...

1984 Ford Laser•10/16/25, 10:40 PM

I plan to move entirely off of and onto anyway so that I can remove the dependency, but good to know