{"version":"2.1.248","anchor":"control-traffic-survives-a-re-authentication-instead-of-bein","canonical_anchor":"control-traffic-survives-a-re-authentication-instead-of-bein","heading":"Control traffic survives a re-authentication instead of being dropped","tier":"notice","area":"Control Protocol","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/control-traffic-survives-a-re-authentication-instead-of-bein","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Control traffic survives a re-authentication instead of being dropped\n\nControl responses and cancellations survive re-authentication instead of being dropped mid-flight.\n\n**What**\n\nSending a control response, cancelling a control request and sending a result no longer bail out early during 401 recovery. All three go through one write path now. Cancelling a request that was a dialog you already declined is retracted locally without a network round trip.\n\n**Evidence**\n\n`Local-only retract of a declined dialog forward request_id=`\n\n- Area: Control Protocol\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}