RELEASED: Public: March 5, 2025
Resolved issues
- The stack trace for a WebSocket agent in HA controllers no longer displays an
HTTP 500 Server errorinstead of the intendedHTTP 502 Bad Gateway error(BEE-55642) -
Under some conditions, an High Availability (HA) controller replica proxying a WebSocket agent connection to another replica might produce an
HTTP 502 Bad Gateway error. Due to an error, the replica instead produced an HTTP 500 error and printed a confusing stack trace in the controller log.