{"version":"2.1.271","anchor":"artifact-auto-react-fork-fallback-now-distinguishes-a-cap","canonical_anchor":"artifact-auto-react-fork-fallback-now-distinguishes-a-cap","heading":"Artifact auto-react: fork-fallback now distinguishes a 'cap' reason","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-auto-react-fork-fallback-now-distinguishes-a-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact auto-react: fork-fallback now distinguishes a 'cap' reason\n\nArtifact comment auto-reply fallback now tracks a distinct 'hit a cap' reason in telemetry\n\n**What**\n\nWhen Claude's automatic reaction to an Artifact comment falls back after a failed \"rehand\" attempt (handing the comment back to Claude to answer), it now checks whether the failure reason was hitting a cap (a limit), and logs a separate telemetry event, `fork_rehand_fallback_cap`, distinct from the generic `fork_rehand_fallback` event used for other fallback causes.\n\n**Why**\n\nThis lets the team distinguish fallbacks caused by hitting a limit from other kinds of fallback failures, which doesn't change what users see but improves diagnosis of this feature.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}