Disable alarms for SQLite in DO (#17185)

src/content/changelogs/durable-objects.yaml

@@ -5,6 +5,11 @@ productLink: "/durable-objects/"
 productArea: Developer platform
 productAreaLink: /workers/platform/changelog/platform/
 entries:
+  - publish_date: "2024-09-27"
+    title: Alarms disabled in (beta) SQLite-backed Durable Object classes
+    description: |-
+      An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
+
   - publish_date: "2024-09-26"
     title: (Beta) SQLite storage backend & SQL API availabe on new Durable Object classes 
     description: |-

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

@@ -6,6 +6,12 @@ sidebar:
 
 ---
 
+:::note[Alarms disabled for SQLite in Durable Objects Beta]
+
+An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
+
+:::
+
 ## Background
 
 Durable Objects alarms allow you to schedule the Durable Object to be woken up at a time in the future. When the alarm's scheduled time comes, the `alarm()` handler method will be called. Alarms are modified using the [Storage API](/durable-objects/api/storage-api/), and alarm operations follow the same rules as other storage operations.

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

@@ -199,6 +199,12 @@ The `put()` method returns a `Promise`, but most applications can discard this p
 
   * This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](/durable-objects/api/storage-api/#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
 
+:::note[Alarms disabled for SQLite in Durable Objects Beta]
+
+An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
+
+:::
+
 ### getAlarm
 
 * <code>getAlarm(optionsObjectoptional)</code> : Promise\<Number | null>

src/content/docs/durable-objects/index.mdx

@@ -34,6 +34,13 @@ The new beta version of Durable Objects is available where each Durable Object h
 Storage API billing is not enabled for Durable Object classes using SQLite storage backend. SQLite-backed Durable Objects will incur [charges for requests and duration](/durable-objects/platform/pricing/#billing-metrics). We plan to enable Storage API billing for Durable Objects using SQLite storage backend in the first half of 2025 after advance notice with the following [pricing](/durable-objects/platform/pricing/#sql-storage-billing).
 
 :::
+
+:::note[Alarms disabled for SQLite in Durable Objects Beta]
+
+An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
+
+:::
+
 ***
 
 ## Features