CCloud Releases
Home
Following

Cloud Releases

Service catalogues and updates come from each provider's public product listing and announcements.

Explore

  • Home
  • Latest updates
  • Following

About

  • About
  • Contact
  • Privacy Policy
  • Terms of Use

Providers

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Cloudflare

Not affiliated with any cloud provider. Product names and logos belong to their owners.

  1. Providers
  2. ›Cloudflare
  3. ›Durable Objects
  4. ›Update

Feature•Mar 15, 2026

Access Durable Object name via `ctx.id.name`

Durable ObjectsCloudflare · Developer platform

When your Worker accesses a Durable Object via idFromName() or getByName(), the same name is now available on ctx.id.name inside the object — no need to pass it through method arguments or persist it in storage. This brings the runtime behavior in line with the Workers runtime types.

This is especially useful for alarms, where there is no calling client to pass the name as an argument. When an alarm handler runs, ctx.id.name will hold the same name the object was originally accessed with.

import { DurableObject } from "cloudflare:workers"; export class ChatRoom extends DurableObject { async getRoomName() { // ctx.id.name returns the name passed to getByName() or idFromName() return this.ctx.id.name; } } // Worker export default { async fetch(request, env) { const stub = env.CHAT_ROOM.getByName("general"); const roomName = await stub.getRoomName(); return new Response(`Welcome to ${roomName}!`); }, };

ctx.id.name is undefined in the following cases:

  • For Durable Objects created with newUniqueId().
  • When accessed via idFromString(), even if the ID was originally created from a name.
  • For names longer than 1,024 bytes.

This works the same way in local development with wrangler dev as it does in production. Run npm update wrangler to ensure you are on a version with this support.

For more information, refer to the Durable Object ID documentation.

Read the original announcement↗

More from Durable Objects

All Durable Objects updates →
  1. Pending I/O operations allow Durable Objects to continue long-running work without a connected client

    Durable Objects remain active while handling a request from a connected client. This change applies when no client is connected, such as when an agent continues a submitted job after its client disconnects.

    Durable Objects•Feature•Oct 1, 2026
  2. Durable Object name search now supports 128 characters

    Durable Object name searches in the Cloudflare dashboard now accept up to 128 characters, up from 20.

    Durable Objects•Feature•Sep 23, 2026
  3. Workers traces now automatically include JavaScript RPC session spans

    Workers traces can now follow JavaScript RPC calls across Worker boundaries and into Durable Objects. Previously, a trace stopped at the caller's RPC boundary.

    Durable Objects•Feature•Sep 17, 2026
  4. Durable Objects can use up to ten Dynamic Workers concurrently

    Durable Objects can have up to ten distinct Dynamic Workers with in-flight requests, increased from four. This limit applies across all concurrent requests to the same Durable Object because they share an input/output (I/O) context.

    Durable Objects•Feature•Aug 28, 2026
  5. Prevent Durable Object alarm retries when using `ctx.abort()`

    By default, an alarm interrupted by ctx.abort() retries after the Durable Object resets. Pass { retryAlarm: false } when the alarm should stop instead:

    Durable Objects•Feature•Aug 25, 2026