{"version":"2.1.261","anchor":"tengu-sdk-result-telemetry-now-includes-user-message-uuid","canonical_anchor":"tengu-sdk-result-telemetry-now-includes-user-message-uuid","heading":"tengu_sdk_result telemetry now includes user_message_uuid","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/tengu-sdk-result-telemetry-now-includes-user-message-uuid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### tengu_sdk_result telemetry now includes user_message_uuid\n\nSDK session-result telemetry now includes the user message id being processed at session end.\n\nSDK and headless session-result telemetry events (`tengu_sdk_result`), covering the crash, terminated, and error_during_execution subtypes, now include a `user_message_uuid` field identifying the user message the turn was processing when the session ended, alongside existing fields like `subtype` and `duration_ms`.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}