[gows] - Webhooks stop sending until session reconnect #1456
Description
Describe the bug
Since updating to version 2025.9.8, WAHA with the GoWS engine (paid tier) intermittently stops sending webhooks for both incoming and outgoing messages.
At the same time, new messages also stop appearing in the dashboard, even though the session status remains “connected”.
The only workaround is to manually disconnect and reconnect the WhatsApp session — after that, everything resumes working normally.
This issue started immediately after the update and repeats randomly every few hours.
⸻
Version
{
"version": "2025.9.8",
"engine": "GOWS",
"tier": "PLUS"
}
⸻
Steps
To Reproduce
1. Connect a WhatsApp session using the GoWS engine.
2. Enable both incoming and outgoing webhooks.
3. Wait several hours or exchange multiple messages.
4. Notice that:
• Webhooks stop being triggered.
• New messages no longer appear in the dashboard.
• The session still shows as connected.
5. Disconnect and reconnect the session — webhooks and dashboard updates work again.
⸻
Expected behavior
Webhooks should continue to be sent, and messages should keep appearing in the dashboard as long as the session is active and connected.
⸻
Requests - Responses
Webhook endpoints are reachable and consistently return HTTP 200.
No error responses are seen from the WAHA API during the issue.
⸻
Docker Logs
No relevant errors appear in docker logs.
Only regular heartbeat and occasional “message received” entries are logged before the issue occurs.
⸻
Additional context
This problem began immediately after upgrading to version 2025.9.8 (GoWS).
It appears the internal message/event listener stops functioning after a few hours of uptime, causing both webhook dispatch and dashboard updates to freeze.
Manual reconnection always restores normal behavior temporarily.
