{"version":"2.1.309","anchor":"re-fetch-of-attachment-files-that-did-not-arrive-on-a-user-m","canonical_anchor":"re-fetch-of-attachment-files-that-did-not-arrive-on-a-user-m","heading":"Missing attachments on a message can be fetched again","tier":"soon","area":"Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/re-fetch-of-attachment-files-that-did-not-arrive-on-a-user-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Missing attachments on a message can be fetched again\n\nWhen files attached to your message did not arrive, Claude Code can fetch them again and tell Claude which ones are still missing\n\n**What**\n\nWhen you attach files to a message, Claude Code can now check whether they actually arrived on disk. If some are missing, it fetches them again. If they still cannot be found, it tells Claude which files are lost. The result can be one of these:\n\n- all files there\n\n- fetched again\n\n- lost\n\n- stopped\n\n- not fetched because of settings\n\n- too slow\n\nIt covers a prompt that was cut off and a follow-up prompt. It falls back to off unless it is switched on remotely.\n\n**Why**\n\nIn remote sessions or sessions connected through a bridge (a link to another app), attachments sometimes do not arrive. Without this, Claude could refer to files it never received.\n\n- Flag `tengu_mossy_anchor`: Not enough to say (read for one account on one subscription tier against v2.1.309; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Attachments\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}