John

Yes! [](https://waha.devlike.pro/docs/how-to/plus-version/#tiers)

can confirm that 2025.10.3 has the same issue: proof: ``` 16/10/2025 17:51:53[17:51:53.177] INFO (10): github.com/devlikeapro/gows/gows.(*GoWS).reissueEvent(0xc0000d6a00?, {0x1163620?, 0xc0012053b0?}) {"engine":"gows"} 16/10/2025 17:51:53[17:51:53.177] INFO (10): /app/src/gows/gows.go:63 +0x2a9 {"engine":"gows"} 16/10/2025 17:51:53[17:51:53.177] INFO (10): created...

I'm on that version. Sorry, forgot to specify. [](https://waha.devlike.pro/docs/how-to/plus-version/#tiers)

I'm still seeing this issue - Upgraded to version 2025.10.3 [](https://waha.devlike.pro/docs/how-to/plus-version/#tiers)

Of course yes! [](https://waha.devlike.pro/docs/how-to/plus-version/#tiers)

Sent the instance logs from the "working" state to the "failed" current status. Hope it suffices, if not throw me another message. I'm sure we'll figure it out. [](https://waha.devlike.pro/docs/how-to/plus-version/#tiers)

Hey, I have this strange behavior in one of my sessions and happens from time to time. What do you need to debug? [](https://waha.devlike.pro/docs/how-to/plus-version/#tiers)

+1! [](https://waha.devlike.pro/docs/how-to/plus-version/#tiers)

I found useful to use a cadence control, like a message queue, using Redis. Basically incrementing (INCR) a key with a timestamp will do the trick, but you can also...

Having the same issue here!