{"version":"2.1.246","anchor":"remote-tool-calls-have-a-distinct-code-for-unverified-approv","canonical_anchor":"remote-tool-calls-have-a-distinct-code-for-unverified-approv","heading":"Remote tool calls have a distinct code for unverified approvals","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/remote-tool-calls-have-a-distinct-code-for-unverified-approv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Remote tool calls have a distinct code for unverified approvals\n\nA remote tool call whose approval couldn't be verified now gets its own distinct failure message.\n\n**What**\n\nA remote tool call whose approval could not be verified now ends as `approval_unverified` with its own message, rather than being lumped in with dropped, timed-out or transport errors.\n\n**Details**\n\n- The classifier checks this case against the originating call before falling through to the generic transport-error path.\n\n**Evidence**\n\n`approval_unverified`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}