From fdb513e0182ca4ab45f8323d21cefdea25030353 Mon Sep 17 00:00:00 2001 From: Rodrigo Mansueli Date: Wed, 20 May 2026 18:08:16 -0300 Subject: [PATCH] Update apps/docs/content/troubleshooting/edge-functions-worker-timeouts-and-websocket-drops.mdx Co-authored-by: Lakshan Perera --- .../edge-functions-worker-timeouts-and-websocket-drops.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/troubleshooting/edge-functions-worker-timeouts-and-websocket-drops.mdx b/apps/docs/content/troubleshooting/edge-functions-worker-timeouts-and-websocket-drops.mdx index 8de4d60f34c..f5b57659afa 100644 --- a/apps/docs/content/troubleshooting/edge-functions-worker-timeouts-and-websocket-drops.mdx +++ b/apps/docs/content/troubleshooting/edge-functions-worker-timeouts-and-websocket-drops.mdx @@ -16,7 +16,7 @@ The supervisor enforces resource limits: - CPU time (soft + hard limits) - Memory usage -It also supports early retirement (`EarlyDrop`) when the isolate appears idle: +It may retire early (`EarlyDrop` event) if the isolate is idle Isolate is considered idle if following conditions are met: - The HTTP response has already been returned. - All `EdgeRuntime.waitUntil()` promises have resolved.