From d189a5ebe90474191370334debbc48fda21ce38e Mon Sep 17 00:00:00 2001
From: emily-shen <69125074+emily-shen@users.noreply.github.com>
Date: Mon, 2 Mar 2026 16:29:53 +0000
Subject: [PATCH] Update known issues for Vitest integration

Removed section on Durable Object alarms from known issues.

https://github.com/cloudflare/workerd/pull/1918
---
 .../docs/workers/testing/vitest-integration/known-issues.mdx  | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/src/content/docs/workers/testing/vitest-integration/known-issues.mdx b/src/content/docs/workers/testing/vitest-integration/known-issues.mdx
index c327fda75a58ddf..12030c7e5fdd517 100644
--- a/src/content/docs/workers/testing/vitest-integration/known-issues.mdx
+++ b/src/content/docs/workers/testing/vitest-integration/known-issues.mdx
@@ -22,10 +22,6 @@ Vitest's [fake timers](https://vitest.dev/guide/mocking.html#timers) do not appl
 
 Dynamic `import()` statements do not work inside `export default { ... }` handlers when writing integration tests with `SELF`, or inside Durable Object event handlers. You must import and call your handlers directly, or use static `import` statements in the global scope.
 
-### Durable Object alarms
-
-Durable Object alarms are not reset between test runs and do not respect isolated storage. Ensure you delete or run all alarms with [`runDurableObjectAlarm()`](/workers/testing/vitest-integration/test-apis/#durable-objects) scheduled in each test before finishing the test.
-
 ### WebSockets
 
 Using WebSockets with Durable Objects with the [`isolatedStorage`](/workers/testing/vitest-integration/isolation-and-concurrency) flag turned on is not supported. You must set `isolatedStorage: false` in your `vitest.config.ts` file.