{"version":"2.1.225","anchor":"error-telemetry-message-extraction-hardened","canonical_anchor":"error-telemetry-message-extraction-hardened","heading":"Error telemetry message extraction hardened","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/error-telemetry-message-extraction-hardened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Error telemetry message extraction hardened\n\nA weird thrown error can no longer break error reporting on its way out.\n\n**What**\n\nReading and augmenting error metadata for telemetry no longer risks throwing from a malformed thrown value.\n\n**Details**\n\n- `telemetryMessage` is read through a guarded helper that type-checks the property and swallows any throw.\n- A companion helper copies missing fields onto an error only when it is a non-null extensible object, also wrapped in try\/catch.\n- Fields already present on the error are never overwritten.\n\n**Evidence**\n\n`telemetryMessage`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}