{"version":"2.1.242","anchor":"handed-off-subscriptions-now-say-yielded-instead-of-interrup","canonical_anchor":"handed-off-subscriptions-now-say-yielded-instead-of-interrup","heading":"Handed-off subscriptions now say \"yielded\" instead of \"interrupted\"","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/handed-off-subscriptions-now-say-yielded-instead-of-interrup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Handed-off subscriptions now say \"yielded\" instead of \"interrupted\"\n\nHanding an Artifact subscription to another session now reads as \"yielded\" instead of looking like a failure.\n\n**What**\n\nWhen a live Artifact subscription is handed to another session, its stopped watch is now reported as \"yielded\" rather than \"interrupt\", \"swept\" or \"killed\", so a deliberate hand-off no longer reads as a failure.\n\n**Details**\n\n- The hand-off path also emits counters for each way it can go wrong: malformed frame, unvettable target, unverified requester, table full, handler threw, stale request, ambiguous answer send, undelivered answer, and two pid-mismatch cases, plus a count of successful hand-backs.\n\n**Evidence**\n\n`yield_handed_back`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}