Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(env): count pending relaunches in the session cap description

Yudhi Armyndharis2cc597c1a470
diff --git a/.env.example b/.env.example
index cb128ade2..c7f7d223b 100644
--- a/.env.example
+++ b/.env.example
@@ -61,8 +61,10 @@ LOG_LEVEL=info # error | warn | info | debug | verbose
# default because the eager status@broadcast read can make WhatsApp revoke some freshly paired
# companions at their first scheduled Web reload. Live status events are unaffected.
STATUS_SEED_ON_READY=false
-# 0 = unlimited. Set a positive integer to cap concurrently running/initializing sessions.
-# A FAILED session is evicted by design (no live engine), so it does not hold a concurrency slot.
+# 0 = unlimited. Set a positive integer to cap concurrently running/initializing sessions, plus
+# sessions waiting to relaunch after a failed reconnect (no engine yet, but their timer starts one).
+# A FAILED session is evicted by design (no live engine, no pending relaunch), so it does not hold a
+# concurrency slot.
# MAX_CONCURRENT_SESSIONS=0
# Graceful-shutdown drain: on SIGTERM/SIGINT the app flips readiness to 503 (so a load balancer stops