Skip to content

Commit 9722467

Browse files
committed
Document that alarms have been re-enabled for SQLite backed DOs
1 parent a891d45 commit 9722467

File tree

3 files changed

+0
-18
lines changed

3 files changed

+0
-18
lines changed

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

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,6 @@ sidebar:
88

99
import { Type } from "~/components";
1010

11-
:::note[Alarms disabled for SQLite in Durable Objects Beta]
12-
13-
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.
14-
15-
:::
16-
1711
## Background
1812

1913
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

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -201,12 +201,6 @@ The `put()` method returns a `Promise`, but most applications can discard this p
201201

202202
* 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.
203203

204-
:::note[Alarms disabled for SQLite in Durable Objects Beta]
205-
206-
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.
207-
208-
:::
209-
210204
### getAlarm
211205

212206
* <code>getAlarm(options <Type text='Object' /> <MetaInfo text='optional' />)</code>: <Type text='Promise<Number | null>' />

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

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -35,12 +35,6 @@ Storage API billing is not enabled for Durable Object classes using SQLite stora
3535

3636
:::
3737

38-
:::note[Alarms disabled for SQLite in Durable Objects Beta]
39-
40-
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.
41-
42-
:::
43-
4438
***
4539

4640
## Features

0 commit comments

Comments
 (0)