{"version":"2.1.277","anchor":"timing-telemetry-added-around-user-message-ingestion-in-head","canonical_anchor":"timing-telemetry-added-around-user-message-ingestion-in-head","heading":"Timing telemetry added around user-message ingestion in headless bridge","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/timing-telemetry-added-around-user-message-ingestion-in-head","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Timing telemetry added around user-message ingestion in headless bridge\n\nHeadless bridge mode now records per-stage timing for incoming user messages and warns if a flag-settle step runs late\n\n**What**\n\nThe 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.\n\n**Why**\n\nThis 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.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}