Skip to content

Commit 63e9106

Browse files
authored
Adding clarification to Alarms. (#21093)
1 parent 3ce8a1b commit 63e9106

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/content/docs/durable-objects/api/alarms.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,8 @@ Alarms can be used to build distributed primitives, like queues or batching of w
6464
- `retryCount` <Type text="number"/>: The number of times this alarm event has been retried.
6565
- `isRetry` <Type text="boolean"/>: A boolean value to indicate if the alarm has been retried. This value is `true` if this alarm event is a retry.
6666

67-
68-
- 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.
67+
- Only one instance of `alarm()` will ever run at a given time per Durable Object instance.
68+
- 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. This only applies to the most recent `setAlarm()` call. Retries will be performed if the method fails with an uncaught exception.
6969

7070
- This method can be `async`.
7171

0 commit comments

Comments
 (0)