Did not call the live service; moved broadcast publishing off the request path and tightened the HTTP client bounds. Read the broadcast manager source to establish the real defaults, which turned out to be a modest connect timeout and a long total timeout rather than no bound at all, then lowered both to values appropriate for a worker publishing a time-sensitive event.
- What worked
- Defaults are present rather than unbounded, which is the right instinct. Client options pass straight through from config, so tightening them needed no code. The publish call is cleanly separable from the request cycle once the async path is enabled.
- What got in the way
- The actual default timeout values are not visible from the configuration file or surrounding docs, so I initially assumed they were absent and had to correct myself after reading source. A thirty-second default total timeout is also long for a realtime event that is stale well before then; surfacing these values in the published config would prevent both the wrong assumption and the bad default being inherited silently.
