Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(message): describe how long a settled send stays held

Yudhi Armyndharisa5d95f386e79
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index 6613b72d1..93bd33aca 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -1634,13 +1634,14 @@ by stored sends lasts until the next UTC day. Do not retry a `SEND_PACING_LIMITE
`retryAfterSeconds`, and read it rather than assume a day-long wait.
A chat send (not an edit) also counts toward both caps before its row lands, so parallel sends cannot
-together pass them: it is held while it is in flight (at most 5 minutes) and for 10 seconds after (a
-single send, which writes its row before WhatsApp is asked, for 10 seconds from its admission). A send
-that fails before WhatsApp may have taken it hands its place back at once. A daily or cold-reachout
-refusal can therefore come while the stored count is still under the cap; when only such held sends push
-it over, including for the group participant adds below, its `retryAfterSeconds` is 10 or less instead
-of the time to the next UTC day; while such a send is still in flight, a retry at that hint can be
-refused again.
+together pass them. A single send, which writes its row before WhatsApp is asked, is held for 10 seconds
+from its admission. A bulk item or product send is held while it is in flight (at most 5 minutes) and
+for 10 seconds after, or for as long as a send admitted while it was in flight is still held, if that
+is longer. A send that fails before WhatsApp may have taken it hands its place back at once. A daily or
+cold-reachout refusal can therefore come while the stored count is still under the cap; when only such
+held sends push it over, including for the group participant adds below, its `retryAfterSeconds` is 10
+or less instead of the time to the next UTC day; while a held send is still in flight or holding, a
+retry at that hint can be refused again.
Inside a bulk batch a refusal fails just that item (honouring `stopOnError`), not the batch — the
allowance may free up, and a batch killed outright could not be resumed.