{"version":"2.1.229","anchor":"killed-sdk-sessions-are-no-longer-reported-as-execution-erro","canonical_anchor":"killed-sdk-sessions-are-no-longer-reported-as-execution-erro","heading":"Killed SDK sessions are no longer reported as execution errors","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/killed-sdk-sessions-are-no-longer-reported-as-execution-erro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Killed SDK sessions are no longer reported as execution errors\n\nDeliberately killed SDK sessions now report as terminated instead of showing up as execution errors.\n\n**What**\n\nA result that ends because the session was terminated now carries the subtype \"terminated\" rather than \"error_during_execution\", so deliberate kills stop showing up as failures.\n\n**Evidence**\n\n`error_during_execution`\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}