Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(faq): give the fixed 30 s SQLite busy timeout

Yudhi Armyndharis19f0d1645484
diff --git a/docs/12-troubleshooting-faq.md b/docs/12-troubleshooting-faq.md
index 2af31bca7..36c2c9be2 100644
--- a/docs/12-troubleshooting-faq.md
+++ b/docs/12-troubleshooting-faq.md
@@ -1102,8 +1102,10 @@ sqlite3 ./data/openwa.sqlite "PRAGMA journal_mode;"
sqlite3 ./data/openwa.sqlite "PRAGMA journal_mode=WAL;"
```
-There is no `DATABASE_SQLITE_BUSY_TIMEOUT`-style env knob — busy handling comes from the
-`better-sqlite3` driver defaults. If locks persist under concurrent sessions, migrate to PostgreSQL.
+There is no `DATABASE_SQLITE_BUSY_TIMEOUT`-style env knob — both SQLite connections wait a
+fixed 30 s on a lock (`SQLITE_BUSY_TIMEOUT_MS`, matching `scripts/backup.sh`'s `.timeout 30000`)
+before failing with `SQLITE_BUSY`, and `better-sqlite3` waits synchronously, so the whole gateway
+stalls for as long as a write waits. If locks persist under concurrent sessions, migrate to PostgreSQL.
**When to Migrate to PostgreSQL:**