{"version":"2.1.295","anchor":"control-request-refusal-log-and-sessions-v2-re-enroll-retry","canonical_anchor":"control-request-refusal-log-and-sessions-v2-re-enroll-retry","heading":"Reworded warning for dropped requests, and a fix for sessions retried after re-enrolment","tier":"notice","area":"Miscellaneous","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/control-request-refusal-log-and-sessions-v2-re-enroll-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Reworded warning for dropped requests, and a fix for sessions retried after re-enrolment\n\nA dropped-request warning now also mentions over-long IDs, and the retry after re-enrolling a device now keeps the retry's result\n\n**What**\n\nThis release has two small changes:\n\n- The warning Claude Code logs when it drops an incoming control request now ends with \"(forged-id refusal suppressed, or the id is too long)\". It used to mention only the suppressed refusal.\n\n- When a session request is refused because the device is untrusted, Claude Code re-enrols the device (registers it again) and tries once more. The result of that second try is now stored where the rest of the code reads it. Before, it was stored in a different place.\n\n**Why**\n\nThe second change can stop a retry that worked from being reported as a failure.\n\n- Area: Miscellaneous\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}