Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(sdk): stop reading a 503 as proof a write never ran

Yudhi Armyndharisd8b738b979e0
diff --git a/sdk/php/README.md b/sdk/php/README.md
index eeac146b6..ce3598e76 100644
--- a/sdk/php/README.md
+++ b/sdk/php/README.md
@@ -63,9 +63,11 @@ so bound any retry. A 429 from the global rate limiter lifts when its window exp
the per-second tier, up to an hour for the hourly tier by default), and `getRetryAfterSeconds()`
carries its `Retry-After` header. A 429 whose `getErrorCode()` is `"SEND_PACING_LIMITED"` is not
transient: do not retry it before `getRetryAfterSeconds()`, which then comes from the body and can
-be hours. `getHeaders()` returns the response headers. In a routed deployment only 503 proves the
-request was never carried out: a forward that fails after the request reached the owner node answers
-502 or 504.
+be hours. `getHeaders()` returns the response headers. A 503 does not prove a write was never
+carried out: the engine answers it when WhatsApp did not confirm in time, and the change may still
+have been applied, so re-read the state before repeating it. In a routed deployment a forward that
+fails before reaching the owner node answers 503, one that fails after the request reached it answers
+502 or 504, and a 503 from the owner itself is relayed unchanged.
```php
use OpenWA\Exceptions\OpenWANotFoundException;
diff --git a/sdk/python/README.md b/sdk/python/README.md
index 1389f7c39..8485b0e37 100644
--- a/sdk/python/README.md
+++ b/sdk/python/README.md
@@ -78,8 +78,11 @@ lifts when its window expires (seconds for the per-second tier, up to an hour fo
tier by default), and `.retry_after_seconds` carries its `Retry-After` header. A 429 whose
`.code` is `"SEND_PACING_LIMITED"` is not transient: do not retry it before
`.retry_after_seconds`, which then comes from the body and can be hours. Every API error also
-exposes the response `.headers`. In a routed deployment only 503 proves the request was never
-carried out: a forward that fails after the request reached the owner node answers 502 or 504.
+exposes the response `.headers`. A 503 does not prove a write was never carried out: the engine
+answers it when WhatsApp did not confirm in time, and the change may still have been applied, so
+re-read the state before repeating it. In a routed deployment a forward that fails before reaching
+the owner node answers 503, one that fails after the request reached it answers 502 or 504, and a
+503 from the owner itself is relayed unchanged.
```python
from openwa import OpenWANotFoundError