Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release
What
The part of the headless/bridge loop that processes incoming user messages now records timings for several stages: deduplication, waiting for flags to settle, running the receive hook, and inlining attachments. If a particular flag-settle wait (related to a component called 'hearth-relay') takes longer than its expected deadline, a warning-level event is now emitted.
Why
This timing data and warning make it possible to spot when user-message processing in headless mode is running slower than expected, and pinpoint which stage is responsible.
