{"version":"2.1.282","anchor":"failures-to-write-a-rendered-image-now-get-their-own-telemet","canonical_anchor":"failures-to-write-a-rendered-image-now-get-their-own-telemet","heading":"Failures to save a converted image are now reported in their own category","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/failures-to-write-a-rendered-image-now-get-their-own-telemet","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Failures to save a converted image are now reported in their own category\n\nClaude Code's usage reports now label \"Could not write image\" failures separately instead of grouping them under \"other\"\n\n**Unclear.** It is not confirmed which helper tool produces this error, though the wording suggests a PDF-to-image converter.\n\n**What**\n\nWhen a helper tool fails while pulling images out of a file, Claude Code sorts the error message into a category for its usage reports. There is now a separate category for failures where the image could not be saved (messages that read \"Could not write image to ... ; exiting\"). These were probably filed as \"other\" before.\n\n**Why**\n\nThis only affects the reports Claude Code sends about failures. What you see while using Claude Code does not change.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}