Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(sdk): stop reading a PHP or Python 503 as a write that never ran

Yudhi Armyndharis501fdc42dccc
diff --git a/sdk/php/src/Exceptions/OpenWAServiceUnavailableException.php b/sdk/php/src/Exceptions/OpenWAServiceUnavailableException.php
index 13677dfff..cf357aaab 100644
--- a/sdk/php/src/Exceptions/OpenWAServiceUnavailableException.php
+++ b/sdk/php/src/Exceptions/OpenWAServiceUnavailableException.php
@@ -11,10 +11,12 @@ namespace OpenWA\Exceptions;
* replied, the socket was down, or the request budget ran out. Retryable, but a catalog 503 can
* persist because WhatsApp may never answer that query, so bound any retry. The non-idempotent
* sends are deliberately left unbounded by the gateway so a slow WhatsApp reply never answers one,
- * and in a multi-node deployment a forwarded request answers 503 only when the owner node was never
- * reached. A forward that fails after the request was sent answers 502 or 504 instead (a plain
- * OpenWAApiException): the owner may already have carried it out, so do not repeat a non-idempotent
- * send on those unchecked.
+ * and in a multi-node deployment a forward that fails before reaching the owner node answers 503. A
+ * 503 from the owner itself is relayed unchanged and means the engine did not confirm, so a bounded
+ * write (group, channel, contact or profile change) may still have been applied; re-read the state
+ * before repeating it. A forward that fails after the request was sent answers 502 or 504 instead
+ * (a plain OpenWAApiException): the owner may already have carried it out, so do not repeat a
+ * non-idempotent send on those unchecked.
*/
class OpenWAServiceUnavailableException extends OpenWAApiException
{
diff --git a/sdk/python/openwa/errors.py b/sdk/python/openwa/errors.py
index 324ca9c61..e35490016 100644
--- a/sdk/python/openwa/errors.py
+++ b/sdk/python/openwa/errors.py
@@ -117,10 +117,12 @@ class OpenWAServiceUnavailableError(OpenWAApiError):
replied, the socket was down, or the request budget ran out. Retryable, but a catalog 503 can
persist because WhatsApp may never answer that query, so bound any retry. The non-idempotent
sends are deliberately left unbounded by the gateway so a slow WhatsApp reply never answers
- one, and in a multi-node deployment a forwarded request answers 503 only when the owner node
- was never reached. A forward that fails after the request was sent answers 502 or 504 instead
- (a plain OpenWAApiError): the owner may already have carried it out, so do not repeat a
- non-idempotent send on those unchecked.
+ one, and in a multi-node deployment a forward that fails before reaching the owner node answers
+ 503. A 503 from the owner itself is relayed unchanged and means the engine did not confirm, so a
+ bounded write (group, channel, contact or profile change) may still have been applied; re-read
+ the state before repeating it. A forward that fails after the request was sent answers 502 or
+ 504 instead (a plain OpenWAApiError): the owner may already have carried it out, so do not
+ repeat a non-idempotent send on those unchecked.
"""