{"version":"2.1.321","anchor":"isreceivedfile-now-fails-closed-on-errors","canonical_anchor":"isreceivedfile-now-fails-closed-on-errors","heading":"The check for received files now answers no when it runs into trouble","tier":"notice","area":"Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/isreceivedfile-now-fails-closed-on-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### The check for received files now answers no when it runs into trouble\n\nClaude Code's check for whether a file was received now answers no on errors, symlinks or very large folders instead of yes\n\n**Unclear.** What a yes or no from this check changes for a reader is not clear.\n\n**What**\n\nClaude Code has a check that decides whether a file counts as a received file. It used to answer yes when something went wrong. Now:\n\n- Symlinks: a symlink (a file that points to another file) no longer gets a yes.\n\n- Too many entries: scanning too many entries no longer gets a yes.\n\n- Errors: an error once scanning has started now answers no, and is logged.\n\n**Why**\n\nWhen it is unclear where a file came from, Claude Code now assumes it was not received rather than assuming it was.\n\n- Area: Attachments\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}