[Feature Request][NOWEB] - Hide "auto-restart" from API (STARTING => WORKING status changes)

[App-developer-269]

Describe the bug

When the dashboard tab is active everything fine, but when i close the dashboard tab the session are Auto-restarting.

{
  "version": "2025.1.06",
  "engine": "NOWEB",
  "tier": "PLUS"
}

Docker Logs

i have attached logs for both situation when the dashboard is active and when it is not active.

Additional context

env variables
WAHA_GOWS_PATH=/app/gows
WAHA_GOWS_SOCKET=/tmp/gows.sock
WAHA_LOCAL_STORE_BASE_DIR=/sessions
WAHA_LOG_FORMAT=PRETTY
WAHA_LOG_LEVEL=info
WAHA_MEDIA_STORAGE=LOCAL
WAHA_ZIPPER=ZIPUNZIP
WHATSAPP_API_SCHEMA=http
WHATSAPP_DEFAULT_ENGINE=NOWEB
WHATSAPP_DOWNLOAD_MEDIA=false

1.dashboard is active

2.dashboard is closed

[devlikepro]

Hi! websocket reconnects every now and then, by default every 30 minutes, so session can move from WORKING to STARTING and back - that' normal behaviour

When you perform API request to the session that currently restarting - it wait in most cases for 5 seconds, so you shouldn't notice it (but shit happens, yeah)

[devlikepro]

btw, GOWS engine doesn't have this auto restart. But it can reconnects (WORKING=>STARTING=>WORKING) due to keep alive settings or 503 from server

[App-developer-269]

Hi! websocket reconnects every now and then, by default every 30 minutes, so session can move from WORKING to STARTING and back - that' normal behaviour

When you perform API request to the session that currently restarting - it wait in most cases for 5 seconds, so you shouldn't notice it (but shit happens, yeah)

@devlikepro Thank you for quick response

Every session on my server has good traffic, like everyday for 5 hr's a every session send's 3 to 8 message's every minute.
This is because i am worried about session auto restarting.

What do think should i worry about this or is there any way to stop this behavior.

[devlikepro]

You can add a retry on your end if you get the response about a session in STARTING status

You'll get 422 Unprocessable Entity HTTP response with response:

{
    "error": "Session status is not as expected. Try again later or restart the session",
    "session": "sessionName",
    "status": "STARTING",
    "expected": ["WORKING"]
}

in this case it's safe to try again (or any other errors, usually)

[App-developer-269]

Is it possible to change the auto restarting behavior of session or increase the timer of auto restart,
without any weird errors/warnings.

[devlikepro]

Is it possible to change the auto restarting behavior of session or increase the timer of auto restart,

No, it's good practice from real expreience with NOWEB engine we've had. Otherwise it stops working properly.

We probably could log it as "warning" not error and hide from the API that sessions is restarting right now (just add timeout to HTTP API call that would wait until the session gets back to WORKING)
We'll check this!

[IchthysMaranatha]

Yes, something to reduce webhook traffic would be nice for session.status. If we could further filter session.status (eg session.status.failed) so as to pick what is needed for webhook, that would also be nice.