Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(migration): say an oversized import can also get 503

Yudhi Armyndharis93f25ff08d10
diff --git a/docs/14-migration-guide.md b/docs/14-migration-guide.md
index 54d8b2bea..5ff1d0974 100644
--- a/docs/14-migration-guide.md
+++ b/docs/14-migration-guide.md
@@ -127,7 +127,9 @@ curl -X POST 'http://localhost:2785/api/infra/import-data' \
> [!IMPORTANT]
> **The import is one request, bounded by the target's `BODY_SIZE_LIMIT`** (default `25mb`); a larger
-> file is refused with `413`. Compare `ls -l data-backup.json` with that limit before Step 4. If the
+> file is refused with `413`, or with `503` and `Retry-After` once it is also above half the in-flight
+> body budget (twice `BODY_SIZE_LIMIT` at the default budget). Retrying does not help either way; raise
+> the limit as below, which clears both because the default budget scales with it. Compare `ls -l data-backup.json` with that limit before Step 4. If the
> file is bigger, set `BODY_SIZE_LIMIT` on the target to at least its size (for example `50mb`) and
> restart, since the value is read at boot; put it back afterwards, because it applies to every route.
> An explicit `INFLIGHT_BODY_BUDGET_BYTES` must stay at least twice the file size, because one caller