{"version":"2.1.299","anchor":"attachment-ask-end-reasons-no-answer-vs-withdrawn-outcomes","canonical_anchor":"attachment-ask-end-reasons-no-answer-vs-withdrawn-outcomes","heading":"Unanswered and withdrawn attachment requests are now told apart","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/attachment-ask-end-reasons-no-answer-vs-withdrawn-outcomes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Unanswered and withdrawn attachment requests are now told apart\n\nAn attachment request that ends now reports either that no answer came, with the wait time, or that it was withdrawn\n\n**Unclear.** Which feature these attachment requests belong to, and whether it is available, is not stated.\n\n**What**\n\nWhen a request about an attachment ends without success, Claude Code now gives one of two outcomes:\n\n- \"no_answer\": no reply came. This includes how long it waited and whether a waiting time limit had been announced.\n\n- \"withdrawn\": the request was taken back.\n\nClaude Code also now records withdrawals in its usage reporting.\n\n**Why**\n\nA pending request that is taken back can now be told apart from one that simply got no answer.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}