{"version":"2.1.290","anchor":"new-system-message-subtype-file-attachments-missing","canonical_anchor":"new-system-message-subtype-file-attachments-missing","heading":"Messages with file attachments: missing-file notice and no queue merging","tier":"use","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/new-system-message-subtype-file-attachments-missing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Messages with file attachments: missing-file notice and no queue merging\n\nA new file_attachments_missing message reports attachments that did not arrive, and queued messages with attachments are no longer merged\n\n**What**\n\nMessages sent to Claude can carry file attachments. Two changes affect how those messages are handled:\n\n- A new system message type, `file_attachments_missing`, reports which attachments on an incoming message did not arrive. For each file it gives a reason: `download`, `too_large`, `write`, `no_token`, `not_finished` or `count_cap`. One finding says only Claude Code Remote workers send it. The SDK (the kit for building programs on top of Claude Code) treats it like other informational notices such as `instruction_size_warning`.\n\n- When messages are waiting in a queue, Claude Code sometimes combines them into one. Queued messages that have file attachments and are not set to ask Claude a question (`shouldQuery` false) are no longer combined.\n\n**Why**\n\nPrograms built on the SDK may start receiving the new message type and can tell users which files did not arrive and why. Not combining queued messages that have attachments keeps each attachment with its own message.\n\n- Area: SDK\n- Names: `file_attachments_missing`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}