[Feature Request] Add a FROZEN Status for Temporarily Disabled Sessions

[Sabyrzhanuly]

I wanted to suggest an improvement. Could you add an additional status besides STOPPED? For example, I have sessions that are temporarily disabled but don’t need to be deleted. However, there’s an issue with restarting these sessions when updating WAHA.

For instance, a FROZEN status could be implemented, and such sessions wouldn’t be affected at all until they are manually started.

[devlikepro]

Hi!
Starting from 2024.10.5 WAHA tracks "running" sessions and only restart those that were "running" after update (#491)
Looks like you're using WHATSAPP_RESTART_ALL_SESSIONS=True flag, right?

Try doing the following next time when updating WAHA:

1. Save list of "running/working" session (just in case something goes wrong, so you can start it manually)
2. Remove WHATSAPP_RESTART_ALL_SESSIONS=True
3. Update/Restart container

It should start only previously "running" sessions.
If you hit "stop" via API or Dashboard - WAHA remembers that the session was stopped and will not restart it on next update/server restart.

Here's what running sessions mean: