Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs: align the engineLoaded, delete and status revoke notes

Yudhi Armyndharis72b59146fa96
diff --git a/docs/13-horizontal-scaling.md b/docs/13-horizontal-scaling.md
index 18db2edf3..b887665d1 100644
--- a/docs/13-horizontal-scaling.md
+++ b/docs/13-horizontal-scaling.md
@@ -73,7 +73,8 @@
> and `memoryUsage` is this process's. `engineLoaded` is the exception, since it also counts a live
> claim by another node. With routing on, `GET /api/sessions/:sessionId` is forwarded to the owner, so
> its answer is the owner's; `start`, `stop`, `logout` and `force-kill` are forwarded the same way, so a
-> `true` means they can act. Without `NODE_URL` nothing is forwarded, so a node that does not hold the
+> `true` means `stop`, `logout` and `force-kill` can act (and `start` answers `400`, as it does on the
+> owner). Without `NODE_URL` nothing is forwarded, so a node that does not hold the
> session still reports `true` but cannot act on it: `start` and `stop` answer `409` there, and `logout`
> and `force-kill` answer `400`.
>
diff --git a/docs/29-engine-capability-matrix.md b/docs/29-engine-capability-matrix.md
index 326c85285..7ec1aec7e 100644
--- a/docs/29-engine-capability-matrix.md
+++ b/docs/29-engine-capability-matrix.md
@@ -984,6 +984,8 @@ adapter boundary — none silently stubs.
`forEveryone=true` on a message the account cannot revoke (not its own, and not in a group it
administers) falls back to that same delete-for-me, as whatsapp-web.js does. WhatsApp ignores such
a revoke while the send still resolves, so sending it would report a deletion that never happened.
+ When the group's member list shows no row the gateway can identify as the account, admin status is
+ unknown and the revoke is still sent.
## 29.8 Snapshot summary
diff --git a/src/modules/status/status.controller.ts b/src/modules/status/status.controller.ts
index 3106fe9c3..bcd081d3d 100644
--- a/src/modules/status/status.controller.ts
+++ b/src/modules/status/status.controller.ts
@@ -181,9 +181,9 @@ export class StatusController {
status: 403,
description:
"Key lacks OPERATOR role; on whatsapp-web.js, the id is not one of the account's own statuses; on " +
- 'Baileys, the status was not posted by this session in the last 24 hours (or was posted before a ' +
- 'restart, from the phone or from another node), so its recipients are unknown and the revoke cannot ' +
- 'be addressed to them.',
+ 'Baileys, the status was not posted by this session in the last 24 hours (or was posted before the ' +
+ 'session last started or reconnected, before a restart, from the phone or from another node), so its ' +
+ 'recipients are unknown and the revoke cannot be addressed to them.',
})
@ApiResponse({ status: 409, description: ENGINE_NOT_READY_409 })
@ApiResponse({ status: 404, description: SESSION_NOT_STARTED_404 })