{"version":"2.1.223","anchor":"undelivered-attachments-are-reported-as-a-tool-error","canonical_anchor":"undelivered-attachments-are-reported-as-a-tool-error","heading":"Undelivered attachments are reported as a tool error","tier":"notice","area":"Teammate Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/undelivered-attachments-are-reported-as-a-tool-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Undelivered attachments are reported as a tool error\n\nAttachments that fail to send are now named as errors instead of falsely reported as delivered.\n\n**What**\n\nThe teammate message tool used to always return \"Message delivered to user.\" with a count of attachments, regardless of what happened to them. Attachments that failed to upload are now named in the result.\n\n**Details**\n\n- Failed attachments are listed with their path and the error that occurred.\n- The tool result is flagged `is_error: true` instead of reporting success.\n- The result text instructs the model to tell the user which attachments were not delivered and why.\n\n**Evidence**\n\n`could NOT be delivered:`\n\n- Area: Teammate Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}