{"version":"2.1.260","anchor":"remote-tools-stalled-call-telemetry-distinguishes-taken-back","canonical_anchor":"remote-tools-stalled-call-telemetry-distinguishes-taken-back","heading":"Remote-tools stalled-call telemetry distinguishes taken-back vs cancelled","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/remote-tools-stalled-call-telemetry-distinguishes-taken-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Remote-tools stalled-call telemetry distinguishes taken-back vs cancelled\n\nStalled remote-tool call telemetry now distinguishes taken-back from cancelled outcomes.\n\nWhen a remote-tools call stalls past its deadline, internal telemetry now records more specific outcomes: whether the call was taken back before any write carried it, or cancelled while a write was already in flight. A new `unconfirmed` outcome (`write_unresolved`) is also recorded when the carrying write never resolves by the deadline.\n\n- Area: Elsewhere\n- Names: `write_unresolved`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}