{"version":"2.1.257","anchor":"more-granular-refusal-reasons-for-remotecross-machine-tool","canonical_anchor":"more-granular-refusal-reasons-for-remotecross-machine-tool","heading":"More granular refusal reasons for remote\/cross-machine tool calls","tier":"notice","area":"Remote Tool Serving","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/more-granular-refusal-reasons-for-remotecross-machine-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### More granular refusal reasons for remote\/cross-machine tool calls\n\nRefused cross-machine tool calls now explain why: stale, queue full, rate limited, duplicate, withdrawn or result lost.\n\nThe refusal-reason map for remote, cross-machine tool calls gained several new cases beyond the prior generic ones: `stale`, `queue_full`, `rate_limited`, `duplicate_call`, `withdrawn`, and `result_lost`, each with a human-readable explanation (for example `queue_full` reports \"that machine was at one of its capacity limits\"). These surface when a call to another machine in a session is refused.\n\n- Area: Remote Tool Serving\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}