how can I view storage.kv/_cf_KV items for remote durable objects?

S

scruffy•11/6/25, 10:35 AM

Hihi! If I spin up a Durable Object to store session data via the KV API and give the data an expiry via TTL, will the Durable Object still exist after the data's expired? If so, is there any residual wrapper that might incur storage costs?

Sscruffy Hihi! If I spin up a Durable Object to store session data via the KV API and giv...

L

Larry•11/6/25, 12:19 PM

Workers KV has expiration dates but the KV inside a DO does not. You'd have to implement that yourself, or use Workers KV.

KKunal Verma how can I view storage.kv/_cf_KV items for remote durable objects?

L

Larry•11/6/25, 12:30 PM

You can add a method on the remote DO that returns it and then call that method remotely using Workers RPC. So,

this.env.REMOTE_DO.getByName('remote-instance-name').get_cf_KV()

this.env.REMOTE_DO.getByName('remote-instance-name').get_cf_KV()

this.env.REMOTE_DO.getByName('remote-instance-name').get_cf_KV()

this.env.REMOTE_DO.getByName('remote-instance-name').get_cf_KV(). If you are going to call the remote DO more times, I recommend that you two-step it and put the the remote DO stub in a variable. So:

const remoteStub = this.env.REMOTE_DO.getByName('remote-instance-name');
const remote_cf_KV = remoteStub.get_cf_KV();

const remoteStub = this.env.REMOTE_DO.getByName('remote-instance-name');
const remote_cf_KV = remoteStub.get_cf_KV();

const remoteStub = this.env.REMOTE_DO.getByName('remote-instance-name');
const remote_cf_KV = remoteStub.get_cf_KV();

const remoteStub = this.env.REMOTE_DO.getByName('remote-instance-name');
const remote_cf_KV = remoteStub.get_cf_KV();

if you are using id's instead of instance names its:

const remoteId = this.env.REMOTE_DO.getIdFromString('23abc...');  // 64 byte opaque hex
const remoteStub = this.env.REMOTE_DO.get(remoteId);
const remote_cf_KV = remoteStub.get_cf_KV();

const remoteId = this.env.REMOTE_DO.getIdFromString('23abc...');  // 64 byte opaque hex
const remoteStub = this.env.REMOTE_DO.get(remoteId);
const remote_cf_KV = remoteStub.get_cf_KV();

const remoteId = this.env.REMOTE_DO.getIdFromString('23abc...');  // 64 byte opaque hex
const remoteStub = this.env.REMOTE_DO.get(remoteId);
const remote_cf_KV = remoteStub.get_cf_KV();

const remoteId = this.env.REMOTE_DO.getIdFromString('23abc...');  // 64 byte opaque hex
const remoteStub = this.env.REMOTE_DO.get(remoteId);
const remote_cf_KV = remoteStub.get_cf_KV();

The only tricky part most of the time is knowing the id or name of the remote DO.

LLarry Workers KV has expiration dates but the KV inside a DO does not. You'd have to i...

S

scruffy•11/6/25, 12:56 PM

thanks for the info. in terms of how to implement in DO, is this only doable via alarms or are there other alternatives?

Bboop If you generate and query by name, you have to supply the jurisdiction. If you u...

1

1534980751438970153470891543•11/6/25, 6:04 PM

that wouldve saved me a lot of work lol....

1

1534980751438970153470891543•11/6/25, 6:06 PM

at least it looks consistent... i added jurisdiction even when using the DO IDs

WWallslide When I'm running a worker locally, how can I clear out my local durable objects

H

Hard@Work•11/6/25, 11:55 PM

You can nuke the

.wrangler

.wrangler

directory, or find the specific DO namespace folder and delete it

T

Tuna•11/7/25, 7:00 AM

HI everyone,

is it possible to mix a durableObject to have Sqllite and also key value?
i have some structured data that i want to save and avoid recalculating, the issue that if i use tabular structure its take for ever to save to sqlite, and if i use a json its failing cause this json is too big.
what is the best practice here?

Ffaraday sql durable objects have synced kv storage

L

Larry•11/7/25, 12:03 PM

As of 2025-09-12 compatiblity date you can do

const x = this.ctx.storage.kv.get(”x”);  // no await

const x = this.ctx.storage.kv.get(”x”); // no await

const x = this.ctx.storage.kv.get(”x”);  // no await

const x = this.ctx.storage.kv.get(”x”); // no await

HHard@Work Not natively, though you should be able to dump the SQL manually

J

Jaiganesh•11/7/25, 1:25 PM

Hi, I was also wondering the same thing...
I am not a developer but an infra guy ... could you please let me know how to dump SQLlite manually?

JJaiganesh Hi, I was also wondering the same thing... I am not a developer but an infra guy...

L

Larry•11/7/25, 3:27 PM

Export ~~for backup~~ is a real hole in Cloudflare's offering at this time. I keep saying, "You have read replicas working. Please, just disconnect one and stick the .sqlite file in R2." The response I keep getting is that idea is just one option that's part of a larger discussion. What I haven't heard is that I'm wrong and it's not as easy as I think, but I do wonder if that's true.

LLarry Export ~~for backup~~ is a real hole in Cloudflare's offering at this time. I ke...

L

lambrospetrou•11/7/25, 3:37 PM

What I haven't heard is that I'm wrong and it's not as easy as I think, but I do wonder if that's true.

I said this multiple times

Right now, you cannot just go and "disconnect one and stick the .sqlite file in R2". It can be done, and that's our plan in some form, but it's not a 2 hour thing our next intern can do.

And to add more colour, it's not that it takes 8 months to do this, it's just that other priorities postponed this work.

Llambrospetrou > What I haven't heard is that I'm wrong and it's not as easy as I think, but I ...

L

lambrospetrou•11/7/25, 3:40 PM

Exporting, backups, migration to some other database system, are all on the roadmap. You can argue they should be higher priority than what is delivered, which is fair, but we can say that for all the other 100 features users are asking for.

Llambrospetrou Exporting, backups, migration to some other database system, are all on the road...

L

Larry•11/7/25, 3:58 PM

When I've been in product manager roles in the past, whenever some annoying person (like I am right now) tells me something should be easy, my reply is, "Not as easy as you think, but if you tell me which of these 10 other things that are near the top of the backlog you would like this to take priority over, we will put it in that spot. Think about it overnight and we'll adjust when you come back in the morning." They usually look at the list and tell me that they think the priorities are pretty close to right as-is. I'm sure that's the case now also.

B

Burrito•11/7/25, 4:22 PM

Not just for backup, real data is also useful for debugging. It's not always simple to manually reproduce a complex database locally.

J

jjjrmy•11/7/25, 4:35 PM

with a Durable Object - is it possible to get the name you used

idFromName

idFromName

idFromName

idFromName from within the DO?

J

jjjrmy•11/7/25, 4:36 PM

in my log I'm seeing:

ctx: DurableObjectState { ...,
  id: DurableObjectId { name: undefined }
}

ctx: DurableObjectState { ...,
  id: DurableObjectId { name: undefined }
}

ctx: DurableObjectState { ...,
  id: DurableObjectId { name: undefined }
}

ctx: DurableObjectState { ...,
  id: DurableObjectId { name: undefined }
}

Jjjjrmy with a Durable Object - is it possible to get the name you used `idFromName` fro...

L

Larry•11/7/25, 4:43 PM

It is not unless you pass it in somehow. Many people have an init() method that they call at the right moment(s) that sticks it in storage. I put the name in a header that my fetch handler plucks out of the header and populates. That only works for me because I never create new instances via Workers RPC. My instances are always created with an HTTP call (either a real fetch/Request or the WebSocket upgrade request).

J

jjjrmy•11/7/25, 4:53 PM

I'm basically using all RPC calls I think

J

jjjrmy•11/7/25, 4:53 PM

so why does it have the

{ name : undefined }

{ name : undefined }

{ name : undefined }

{ name : undefined }?

J

jjjrmy•11/7/25, 4:53 PM

like not that I set it as undefined, what's even the point of it being there

Jjjjrmy like not that I set it as undefined, what's even the point of it being there

L

lambrospetrou•11/7/25, 4:55 PM

The type is for

DurableObjectId

DurableObjectId

DurableObjectId

DurableObjectId, which is used both on the caller side of the RPC and inside the DO. In the caller side the

.name

.name

.name

.name will be populated correctly. The fact it's not populated inside the DO is a long-term known bug.

Llambrospetrou The type is for `DurableObjectId`, which is used both on the caller side of the ...

J

jjjrmy•11/7/25, 4:59 PM

so is there a case when it should show?

Jjjjrmy so is there a case when it should show?

L

lambrospetrou•11/7/25, 5:00 PM

Inside the DO, it will never show right now, until the bug is fixed internally.

J

jjjrmy•11/7/25, 5:00 PM

basically for example I have 2 DOs, each with some data in KV.
I can call

firstDO.index()

firstDO.index()

firstDO.index()

firstDO.index() and

secondDO.index()

secondDO.index()

secondDO.index()

secondDO.index() to get the list of the items. but I want to include the name of the DO in the list. Ideally it could be done within the

index()

index()

index()

index() function and not after.

Jjjjrmy basically for example I have 2 DOs, each with some data in KV. I can call `first...

L

lambrospetrou•11/7/25, 5:03 PM

As Larry said, at the moment the workaround is to store the name inside the DO storage during the DO initialization phase if you have one, otherwise in any of the followup calls, or you pass it all the time as argument. What you do and how depends on your use-case. Cumbersome, but unfortunately these are the options to have it in there.

J

jjjrmy•11/7/25, 5:05 PM

so anyone trying to fix this well known long-term bug?

J

jjjrmy•11/7/25, 5:06 PM

basically my point is if you have to pass it in to the DO - I might as well just include the data outside of the DO since that's where it's coming from anyways.

Jjjjrmy so anyone trying to fix this well known long-term bug?

L

lambrospetrou•11/7/25, 5:11 PM

You can track this bug in https://github.com/cloudflare/workerd/issues/2240

Llambrospetrou The type is for `DurableObjectId`, which is used both on the caller side of the ...

J

João Castro•11/7/25, 5:32 PM

Since it is never populated inside the DO (and I suppose this won't be fixed short-term), I think it would be better and cause less confusion to have different type definitions for each place, where the one in the DO instance wouldn't have the

.name

.name

.name

.name property

N

Need_Not•11/7/25, 6:02 PM

Trying to move a KV DO to SQLite and I know I'll have to delete it and create a new one. But how do you do that? what does the migration look like? Do I have to completely remove the binding from wrangler, build then readd it?

N

Need_Not•11/7/25, 6:04 PM

do i simply do this?

        {
          "tag": "v3",
          "deleted_classes": [
            "UserCreditsObject"
          ],
          "new_sqlite_classes": [
            "UserCreditsObject"
          ]
        }

        {
          "tag": "v3",
          "deleted_classes": [
            "UserCreditsObject"
          ],
          "new_sqlite_classes": [
            "UserCreditsObject"
          ]
        }

        {
          "tag": "v3",
          "deleted_classes": [
            "UserCreditsObject"
          ],
          "new_sqlite_classes": [
            "UserCreditsObject"
          ]
        }

        {
          "tag": "v3",
          "deleted_classes": [
            "UserCreditsObject"
          ],
          "new_sqlite_classes": [
            "UserCreditsObject"
          ]
        }

L

ldenoue•11/7/25, 6:39 PM

Just got issues with SQLite today in my DO where I stored user tables. "Error: Exceeded allowed rows written in Durable Objects free tier". Which is really strange since I'm only storing a few rows (8 users!) and 100 rows in a table called "transcripts".

J

jjjrmy•11/7/25, 6:51 PM

So they just call

setIdentifier

setIdentifier

setIdentifier

setIdentifier every time they "get" an Actor instance (which is a Durable Object) and refer to

this.identifier

this.identifier

this.identifier

this.identifier rather than try to parse the name out of the id. It's very little code and works the same in dev and production.

Jjjjrmy So they just call `setIdentifier` every time they "get" an Actor instance (which...

L

lambrospetrou•11/7/25, 6:55 PM

Personally, I suggest against this for what's worth. Doing explicitly as it suits your use-case, either once at the beginning/creation, or in every request.

Jjjjrmy So they just call `setIdentifier` every time they "get" an Actor instance (which...

L

Larry•11/7/25, 8:00 PM

I'm basically using all RPC calls I think

I hear people say this and I always wonder how users enter the system? It's got to be HTTP or WebSockets, no?

Llambrospetrou Personally, I suggest against this for what's worth. Doing explicitly as it suit...

L

Larry•11/7/25, 8:24 PM

What exactly are you recommending against and why?

LLarry What exactly are you recommending against and why?

L

lambrospetrou•11/7/25, 8:26 PM

Doing a 2nd call to the DO all the time for every request to set the name identifier.

Llambrospetrou Doing a 2nd call to the DO all the time for every request to set the name identi...

J

jjjrmy•11/7/25, 8:46 PM

like I was thinking

firstDO.withIdentifier('user:123').index()

firstDO.withIdentifier('user:123').index()

firstDO.withIdentifier('user:123').index()

firstDO.withIdentifier('user:123').index()

LLarry > I'm basically using all RPC calls I think I hear people say this and I always ...

J

jjjrmy•11/7/25, 8:47 PM

so I use a normal Hono router on a worker for the routing.
I use the DO's

fetch()

fetch()

method for handling the websockets.

everything else is done through RPC

J

jjjrmy•11/7/25, 8:48 PM

app.get("/:id", HonoAuthMiddleware, BindDurableObjectMiddleware, async (c) => {
  const id = c.req.param("id");

  const notification = await c.var.notifications.get(id);

  if (!notification) return c.body(null, 204);

  return c.json(notification);
});

app.get("/:id", HonoAuthMiddleware, BindDurableObjectMiddleware, async (c) => {
  const id = c.req.param("id");

  const notification = await c.var.notifications.get(id);

  if (!notification) return c.body(null, 204);

  return c.json(notification);
});

app.get("/:id", HonoAuthMiddleware, BindDurableObjectMiddleware, async (c) => {
  const id = c.req.param("id");

  const notification = await c.var.notifications.get(id);

  if (!notification) return c.body(null, 204);

  return c.json(notification);
});

app.get("/:id", HonoAuthMiddleware, BindDurableObjectMiddleware, async (c) => {
  const id = c.req.param("id");

  const notification = await c.var.notifications.get(id);

  if (!notification) return c.body(null, 204);

  return c.json(notification);
});

J

jjjrmy•11/7/25, 8:49 PM

so really I use the durable object as a class with a store in it, kinda like you'd use something like Pinia for on the frontend.

J

jjjrmy•11/7/25, 8:50 PM

a store has it's state, actions, getters

J

jjjrmy•11/7/25, 8:51 PM

idk why I went with this instead of doing it all through

fetch ()

fetch ()

fetch ()

fetch () and routing it that way

J

jjjrmy•11/7/25, 9:01 PM

@Larry and the

BindDurableObjectMiddleware

BindDurableObjectMiddleware

BindDurableObjectMiddleware

BindDurableObjectMiddleware is what sets the DO to

c.var.notifications

c.var.notifications

c.var.notifications

c.var.notifications