Skip to content

Commit 81350e0

Browse files
Oxyjunvy-ton
andauthored
Apply suggestions from code review
Co-authored-by: Vy Ton <[email protected]>
1 parent 1de19dd commit 81350e0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: The Lifecycle of a Durable Object
2+
title: Lifecycle of a Durable Object
33
pcx_content_type: concept
44
sidebar:
55
order: 3
@@ -39,8 +39,8 @@ A Durable Object can be in one of the following states at any moment:
3939
| **Active in-memory** | The Durable Object runs, in memory, and handles incoming requests. |
4040
| **Idle in-memory non-hibernateable** | The Durable Object waits for the next incoming request/event, but does not satisfy the criteria for hibernation. |
4141
| **Idle in-memory hibernateable** | The Durable Object waits for the next incoming request/event and satisfies the criteria for hibernation. It is up to the runtime to decide when to hibernate the Durable Object. Currently, it is after 10 seconds of inactivity while in this state. |
42-
| **Hibernated** | The Durable Object is removed from memory. |
43-
| **Inactive** | The Durable Object is completely removed from the host process. Might need a cold start. This is the initial state of all Durable Objects. |
42+
| **Hibernated** | The Durable Object is removed from memory. Hibernated WebSocket connections stay connected. |
43+
| **Inactive** | The Durable Object is completely removed from the host process and might need to cold start. This is the initial state of all Durable Objects. |
4444

4545
This is how a Durable Object transitions among these states (each state is in a rounded rectangle).
4646

0 commit comments

Comments
 (0)