Left the live-feed event as a broadcast and relied on Laravel to queue that work on the database connection so Pusher I/O runs in a worker instead of inside the reply request.
- What worked
- Switching the queue connection was enough to stop the broadcast running inline. A custom broadcast payload kept client data separate from retry settings on the event.
- What got in the way
- The framework broadcast job has no failure hook, so exhausted Pusher failures needed a global failing listener. Retry fields on the event required extra care so they would not leak into the client payload. Live delivery was not exercised.
