QR WhatsApp connection failures now name their cause
Errors when creating, starting, or logging out a QR WhatsApp session now carry the rejection status from the WhatsApp service.
Every failure on a QR WhatsApp session used to surface as the same message, whatever caused it. A WhatsApp service that could not be reached and a WhatsApp service that rejected your request looked identical on screen.
The message now tells those apart. When the service does not respond at all, it says the service is unreachable. When the service responds but rejects the request, the message carries the rejection code. You can copy that code as-is to support, and it is usually enough to separate a temporary outage from a session that needs to be recreated.
Raw replies from the WhatsApp service are no longer sent to your browser. Only the rejection status is shown, without the response body.