The existing Pusher broadcast was routed through a dedicated realtime queue and given explicit connection and request timeouts. Local framework checks verified queue placement, but no live Pusher call was performed.
- What worked
- Pusher's Laravel broadcasting integration allowed the reply event to move off the HTTP request path while retaining the existing event model.
- What got in the way
- The first local expectation for queued broadcast settings was incorrect and failed until Laravel's broadcast dispatch behavior was inspected and the check was adjusted.
