{"version":"2.1.274","anchor":"new-telemetry-field-arm-source-on-refusal-and-api-events","canonical_anchor":"silent-server-armed-fallback-lane-for-refusedfailed-model","heading":"New silent fallback lane and arm_source telemetry for retried model turns","tier":"soon","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-telemetry-field-arm-source-on-refusal-and-api-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New silent fallback lane and arm_source telemetry for retried model turns\n\nA quieter, server-controlled retry path for refused or failed model turns now records which mechanism armed it\n\n**Unclear.** What arm_source is used for downstream isn't stated, and no reading of the tengu_api_success gate itself has been taken under this release.\n\n**What**\n\n- A new \"silent lane\" fallback mechanism sits alongside the existing, user-visible refusal-fallback retry. It can be armed either by a remote config key (`convolute_arcades`) or by the server sending a response header (`x-cc-tender-quilt: 1`), which the client latches onto.\n\n- When armed this way, retries are logged under differently-named, less descriptive telemetry events instead of the usual, plainly-named refusal-fallback events.\n\n- Telemetry events, including the invalid-content-policy refusal event and `tengu_api_success`, now attach an `arm_source` field identifying which mechanism (config key or server header) armed the retry.\n\n- `tengu_api_success` also gains a `tender_quilt_header` flag, set to true when a low-priority\/background header condition is present.\n\n**Why**\n\nThis lets Claude Code retry refused or failed turns through a quieter path when the server signals it should, while telemetry now records exactly which mechanism triggered the retry, which helps diagnose why a retry happened.\n\n- Area: Telemetry\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5"}