Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(runbooks): scope the recorded session stop to 0.24.0
Yudhi Armyndharisc3b44347cf6b
diff --git a/docs/11-operational-runbooks.md b/docs/11-operational-runbooks.mdindex 7973fd45c..e67cb5a59 100644--- a/docs/11-operational-runbooks.md+++ b/docs/11-operational-runbooks.md@@ -499,7 +499,9 @@ curl -H "X-API-Key: $API_KEY" http://localhost:2785/api/health | jq '.version'# 11. Verify all sessions# (they reconnect on their own only with AUTO_START_SESSIONS=true; otherwise POST# /api/sessions/{sessionId}/start each one first). A session stopped in step 2 stays down,-# even with AUTO_START_SESSIONS=true, until that explicit start+# even with AUTO_START_SESSIONS=true, until that explicit start, but only when the old image+# was 0.24.0 or later: a stop made on 0.23.7 or earlier is not recorded, so with+# AUTO_START_SESSIONS=true that session starts on its own after the upgradecurl -H "X-API-Key: $API_KEY" \http://localhost:2785/api/sessions@@ -632,8 +634,9 @@ curl -H "X-API-Key: $API_KEY" http://localhost:2785/api/healthit, so a restored session can need re-pairing; for a copy that is consistent by construction, stopthe sessions first (`POST /api/sessions/:id/stop`), or stop the container and archive the volume.A stopped session stays down across restarts, even with `AUTO_START_SESSIONS=true`, so start each-one again with `POST /api/sessions/:id/start` once the backup is copied. The stop is recorded in the-backed-up database, so a restore of that archive keeps the session stopped too.+one again with `POST /api/sessions/:id/start` once the backup is copied. From 0.24.0 the stop is+recorded in the backed-up database, so a restore of that archive keeps the session stopped too; an+archive taken on 0.23.7 or earlier records no stop.**Prerequisites:**