You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/durable-objects/api/alarms.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Notably:
21
21
22
22
- Each Durable Object instance is able to schedule a single alarm at a time by calling `setAlarm()`.
23
23
- Alarms have guaranteed at-least-once execution and are retried automatically when the `alarm()` handler throws.
24
-
- Retries are performed using exponential backoff starting at a two second delay from the first failure with up to six retries allowed.
24
+
- Retries are performed using exponential backoff starting at a 2 second delay from the first failure with up to 6 retries allowed.
25
25
26
26
:::note[How are alarms different from Cron Triggers?]
27
27
@@ -63,7 +63,7 @@ Alarms can be used to build distributed primitives, like queues or batching of w
63
63
64
64
- Called by the system when a scheduled alarm time is reached.
65
65
66
-
- The `alarm()` handler has guaranteed at-least-once execution and will be retried upon failure using exponential backoff, starting at two second delays for up to six retries. Retries will be performed if the method fails with an uncaught exception.
66
+
- The `alarm()` handler has guaranteed at-least-once execution and will be retried upon failure using exponential backoff, starting at 2 second delays for up to 6 retries. Retries will be performed if the method fails with an uncaught exception.
0 commit comments