Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(env): say full Baileys history applies only when linking

Yudhi Armyndharisa5646f905ad2
diff --git a/.env.example b/.env.example
index 048a90b93..425e9dc7e 100644
--- a/.env.example
+++ b/.env.example
@@ -207,8 +207,9 @@ OPENWA_PIDS_LIMIT=2048
# BAILEYS_AUTH_DIR=./data/baileys
# NOTE: proxy egress is configured PER SESSION, on both engines, via the proxyUrl/proxyType fields on
# POST /api/sessions or PATCH /api/sessions/:sessionId/proxy (ADMIN), NOT via environment variables.
-# Pull the FULL message-history archive on connect (large). Off by default: the engine still enables the
-# initial sync (contacts, chats, recent messages, lid mappings) without downloading the entire history.
+# Pull the FULL message-history archive when the device is linked (large; set before linking, an
+# already-linked session must be re-linked). Off by default: the engine still enables the initial
+# sync (contacts, chats, recent messages, lid mappings) without downloading the entire history.
# BAILEYS_SYNC_FULL_HISTORY=false
# Announce the linked device as online when the socket connects. Baileys' default is true, which
# suppresses WhatsApp push notifications on the paired phone while the gateway is connected —