From 2789db78fdca91a5f15280f7518050cee96ac590 Mon Sep 17 00:00:00 2001 From: Jun Lee Date: Fri, 9 May 2025 09:19:36 +0100 Subject: [PATCH] Explicitly mentioning setAlarm can override previously scheduled alarm --- src/content/docs/durable-objects/api/alarms.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/src/content/docs/durable-objects/api/alarms.mdx b/src/content/docs/durable-objects/api/alarms.mdx index d1bbbff1443684..807ae8edf12372 100644 --- a/src/content/docs/durable-objects/api/alarms.mdx +++ b/src/content/docs/durable-objects/api/alarms.mdx @@ -43,6 +43,7 @@ Alarms can be used to build distributed primitives, like queues or batching of w : - Set the time for the alarm to run. Specify the time as the number of milliseconds elapsed since the UNIX epoch. + - If you call `setAlarm` when there is already one scheduled, it will override the existing alarm. ### `deleteAlarm`