{"version":"2.1.225","anchor":"aborted-transport-operations-report-a-consistent-aborted-err","canonical_anchor":"aborted-transport-operations-report-a-consistent-aborted-err","heading":"Aborted transport operations report a consistent 'aborted' error class","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/aborted-transport-operations-report-a-consistent-aborted-err","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Aborted transport operations report a consistent 'aborted' error class\n\nCancelling a connection is now recorded as an abort rather than a generic failure.\n\n**What**\n\nAborts in the direct-connect transport are now classified as aborts in telemetry instead of appearing as generic failures.\n\n**Details**\n\n- the transport rejects with a helper that builds the abort error together with telemetry metadata, rather than constructing a bare error\n- the resulting event carries `errorClass: \"aborted\"`\n\n**Evidence**\n\n`telemetryMessage: \"Operation aborted\"`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}