{"version":"2.1.225","anchor":"sdk-subprocess-errors-carry-an-error-class-and-sanitized-mes","canonical_anchor":"sdk-subprocess-errors-carry-an-error-class-and-sanitized-mes","heading":"SDK subprocess errors carry an error class and sanitized message","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/sdk-subprocess-errors-carry-an-error-class-and-sanitized-mes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### SDK subprocess errors carry an error class and sanitized message\n\nSDK subprocess failures are now grouped by cause with paths and stderr scrubbed from reports.\n\n**What**\n\nErrors from the SDK's subprocess transport are wrapped with a redacted `telemetryMessage` and an `errorClass` so failures can be grouped.\n\n**Details**\n\n- classes include `spawn_failed`, `process_exited_nonzero`, `process_killed_by_signal`, `executable_not_found` and `control_request_failed`\n- covers spawn failures, non-zero exits, signal kills, aborts, control-request failures and error results\n- stderr tails and filesystem paths are redacted before being attached\n\n**Evidence**\n\n`process_killed_by_signal`\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}