{"version":"2.1.285","anchor":"orphaned-permission-answers-now-log-why-they-are-dropped","canonical_anchor":"orphaned-permission-answers-now-log-why-they-are-dropped","heading":"Dropped permission answers now record why they were dropped","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/orphaned-permission-answers-now-log-why-they-are-dropped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Dropped permission answers now record why they were dropped\n\nWhen a permission answer no longer matches a waiting request, Claude Code now records the reason it was dropped\n\n**What**\n\nSometimes an answer to a permission prompt, where you allow or deny an action, arrives when no matching request is waiting. Claude Code drops these answers. Before, it did so silently. Now it records the reason, for example:\n\n- `name_mismatch`\n\n- `already_handled`\n\n- `not_unresolved`\n\nIt also records when such an answer is accepted and queued.\n\n**Why**\n\nNothing you see changes, but this helps track down permission answers that go missing in resumed or remote sessions.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}