[GOWS] - 2026.3.4 - Sessions take a long time to start after server restart

[mateusangelo]

Since updating to version 2026.3.4, I've noticed a significant performance degradation during the server startup process. While previous versions handled session restoration much faster, the current version takes approximately 20 minutes to get 90 sessions into the READY state after a restart.

Environment

WAHA Version: 2026.3.4

Number of sessions: 90

Questions / Investigation

Is this increased delay a deliberate change in the startup logic for stability/anti-ban purposes?

Are there any new parameters in v2026.3.4 to control the concurrency or the delay between session starts?

Specifically, does WHATSAPP_START_SESSION_DELAY or a similar internal throttle have a new default value in this version?

[devlikepro]

Hi! Which database are you using - PostgreSQL, or the standard one (which is SQLite, though it works perfectly fine for 90 sessions)?

[devlikepro]

Is there a WAHA log covering those 20 minutes? It would be very helpful to take a look at them; you can send them to waha@devlike.pro. There haven't been any changes related to this, but it could be a "too many requests" error originating from the WA servers; I’d like to confirm if that is the case.

Could you also try explicitly adding the WAHA_AUTO_START_DELAY_SECONDS variable and see if that helps?

WAHA_AUTO_START_DELAY_SECONDS=2

[devlikepro]

Could you also try a new version and WAHA_AUTO_START_DELAY_SECONDS=2 🙏

2026.4.1 - GOWS - await grpc response when starting a new session - #2012