Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(env): limit the per-conversation ordering claim to ingress

Yudhi Armyndharis92ee84ab8cb8
diff --git a/.env.example b/.env.example
index 2817c830f..7b56535fc 100644
--- a/.env.example
+++ b/.env.example
@@ -756,9 +756,10 @@ WEBHOOK_SSRF_PROTECT=true
# falls back to 7 rather than letting the table grow forever
# Concurrency of the BullMQ workers that process queued webhooks and ingress events. Only meaningful
-# when QUEUE_ENABLED=true. Ordering within one conversation is preserved by a per-conversation lock,
-# so raising these parallelizes unrelated conversations rather than reordering them. Neither pool is
-# isolated per webhook or per conversation:
+# when QUEUE_ENABLED=true. Ingress events keep their order within one conversation through a
+# per-conversation lock, so raising INGRESS_WORKER_CONCURRENCY parallelizes unrelated conversations.
+# Webhook deliveries are not ordered per chat, and raising WEBHOOK_WORKER_CONCURRENCY can reorder
+# deliveries for one chat. Neither pool is isolated per webhook or per conversation:
# - A dead webhook receiver holds a slot for up to WEBHOOK_TIMEOUT per attempt. Once a webhook's
# attempt fails, jobs for it that start afterwards take a per-session slot, at most
# WEBHOOK_DEGRADED_SESSION_CONCURRENCY at a time (the rest wait in the delayed set without