[Question] WAHA session stuck after ~30 days — “Session ‘default’ is already started” & FAILED status

[itajisen]

👉 Kindly use
GitHub Discussions to ask
questions!
I am using WAHA deployed on Railway.
After around 30 days of uptime, the session becomes stuck and cannot be restarted.Symptoms:Dashboard shows:Status: FAILEDError: 422 Unprocessable EntityMessage: “Session ‘default’ is already started.”
Restarting the session does not fix the issue.The WhatsApp account becomes unreachable until I manually re-login.The dashboard also shows:“FAILED: 1”“WEBJS (2026.5.1 CORE) — 30 days up”Environment:Deployment: RailwayWAHA version: 2026.5.1 CORESession name: defaultUptime before failure: ~30 days
Expected behavior:
The session should restart normally or automatically recover after long uptime.Actual behavior:
The session becomes stuck in FAILED state and cannot be restarted.
The system reports that the session is already started even though it is not functioning.
Screenshot:
(attach your dashboard screenshot here)Request:
Please advise how to prevent session lock-up after long uptime, or whether WAHA requires periodic session refresh / re-login.
Is this expected behavior for long-running WAHA deployments on Railway?

[nicolasmdq]

Hi, it's an old WAHA version, try it again with the most recent version and NOWEB core. There have been many recent changes to WhatsApp.