{"version":"2.1.260","anchor":"session-forwarding-outcome-now-classified-rather-than-delete","canonical_anchor":"session-forwarding-outcome-now-classified-rather-than-delete","heading":"Session-forwarding outcome now classified rather than deleted via HTTP","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/session-forwarding-outcome-now-classified-rather-than-delete","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Session-forwarding outcome now classified rather than deleted via HTTP\n\nRemote session forwarding now classifies outcomes directly instead of using an HTTP DELETE.\n\nRemote session forwarding no longer closes a session by sending an HTTP DELETE. Instead, forwarding outcomes are now classified directly: `sent`, `unchanged`, and `conflict_resolved` map to success, while outcomes like `raced`, `lane_full`, `unauthorized`, `deadline`, `failed`, and `aborted` map to failure. This is part of a reworked remote command-forwarding\/session-sync path.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}