{"version":"2.1.223","anchor":"attachment-upload-failures-reported-back-to-the-model-per-fi","canonical_anchor":"attachment-upload-failures-reported-back-to-the-model-per-fi","heading":"Attachment upload failures reported back to the model per file","tier":"notice","area":"Attachments","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/attachment-upload-failures-reported-back-to-the-model-per-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Attachment upload failures reported back to the model per file\n\nAttachments that fail to upload are now reported per file instead of silently vanishing.\n\n**What**\n\nWhen a bridge attachment fails to upload, the tool result now says so per file instead of silently omitting it.\n\n**Details**\n\n- The attachment schema gained an optional `upload_error` string, populated on failure.\n- The tool result splits attachments into delivered and failed sets.\n- A result with any failure is marked as an error and lists each failed path with its error string, alongside a count of attachments that were included.\n\n**Evidence**\n\n`upload_error: w.string().optional()`\n\n- Area: Attachments\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}