{"version":"2.1.234","anchor":"every-attachment-upload-telemetry-point-now-records-which-ro","canonical_anchor":"every-attachment-upload-telemetry-point-now-records-which-ro","heading":"Every attachment-upload telemetry point now records which route was used","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/every-attachment-upload-telemetry-point-now-records-which-ro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Every attachment-upload telemetry point now records which route was used\n\nAttachment uploads now report which route they took on every outcome, success or failure.\n\n**What**\n\nUploads report the lane they took (`repl`, `env_brief_upload`, `env_ccr`, `env_byoc`, `sdk_hosted`, `sdk_hosted_disabled` or `none`) on every outcome: missing token, too large, read failure, bad response, aborted, network error and success. The send events for briefs and user files report it too. Size limits and the provider and privacy refusals are unchanged.\n\n**Details**\n\n- SDK-hosted results can also be flagged as having been rendered locally.\n\n**Evidence**\n\n`upload_lane`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}