{"version":"2.1.280","anchor":"unanswered-control-request-handlers-tracked-across-shutdown","canonical_anchor":"unanswered-control-request-handlers-tracked-across-shutdown","heading":"Unanswered control-request handlers tracked across shutdown","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/unanswered-control-request-handlers-tracked-across-shutdown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Unanswered control-request handlers tracked across shutdown\n\nSDK control connection now tracks handlers for still-pending requests across a shutdown\n\n**What**\n\nThe SDK's control-protocol connection now keeps a new map, `unansweredSettleHandlers`, alongside its existing tracking of in-flight requests. It's used on the path that hands off a `control_response` for requests that are still pending when the process shuts down, passing them to the next process.\n\n**Why**\n\nThis helps ensure that requests still awaiting a response don't lose their response handler when a process shuts down and control passes to the next one.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}