{"version":"2.1.285","anchor":"cloud-file-downloads-record-failure-reasons-and-timings","canonical_anchor":"cloud-file-downloads-record-failure-reasons-and-timings","heading":"Cloud file downloads now record why they fail and how long steps take","tier":"internal","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/cloud-file-downloads-record-failure-reasons-and-timings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Cloud file downloads now record why they fail and how long steps take\n\nDownloading files in cloud sessions now records failure reasons and timings for image preparation, writing and hashing\n\n**Unclear.** Where these totals are sent was not established.\n\n**What**\n\nWhen Claude Code downloads a file for a cloud session and the download fails, it now records a reason instead of failing silently:\n\n- no token\n\n- file too large\n\n- an error\n\n- the web server's status code\n\nIt also records how long each step takes when it prepares an image to include inline (resizing, reducing PNG colours, fitting a size budget), writes the file and computes its checksum. It notes when a PNG image is sent as a JPEG.\n\n**Why**\n\nThis is usage and diagnostic data only and does not change what you see, but it shows attention on how slowly attachments load in cloud sessions.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}