Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(env): name the 503 read timeout next to the Puppeteer error

Yudhi Armyndharis37c6893e320a
diff --git a/.env.example b/.env.example
index 0890e6b4a..947537351 100644
--- a/.env.example
+++ b/.env.example
@@ -138,8 +138,9 @@ STATUS_SEED_ON_READY=false
# PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium
# How long a single browser command may take before it is abandoned, in milliseconds. Unset means
# Puppeteer's own budget (180000 today), so leaving it unset changes nothing. Raise it if a large account
-# (thousands of chats) fails a read with "Runtime.callFunctionOn timed out"; the renderer is still
-# working, the command budget just ran out. Must be a POSITIVE integer no greater than 2147483647:
+# (thousands of chats) fails a read with a 503 "did not answer ... in time" (the chat, group and contact
+# lists) or with "Runtime.callFunctionOn timed out"; the renderer is still working, the command budget
+# just ran out. Must be a POSITIVE integer no greater than 2147483647:
# 0 does not mean "no limit later", it means no timer is armed at all, so a wedged browser holds the
# request forever instead of failing it; and above 2147483647 Node's timer overflows and
# fires after 1 ms, so the browser never finishes launching. The gateway refuses to boot on either.