{"version":"2.1.234","anchor":"resolving-an-artifact-comment-falls-back-when-the-server-ref","canonical_anchor":"resolving-an-artifact-comment-falls-back-when-the-server-ref","heading":"Resolving an artifact comment falls back when the server refuses the session token","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/resolving-an-artifact-comment-falls-back-when-the-server-ref","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Resolving an artifact comment falls back when the server refuses the session token\n\nResolving an artifact comment now retries the plain endpoint when the session token is refused.\n\n**What**\n\nMarking an artifact comment resolved is attempted first against the session-scoped endpoint, and a server refusal of that token no longer fails the action. The client retries the plain resolve endpoint, and the telemetry now tells a refused token apart from a route that was never there.\n\n**Details**\n\n- The refusal is a 403 whose response body carries the marker \"CCR agent tokens cannot call this route\", and only that case triggers the new path.\n- Refusals are logged under `artifact_comment_session_resolve` with the outcome `session_route_ccr_denied`.\n- A 404 from the session route still falls back as before and still logs the older outcome `session_route_fell_back`.\n- The fallback request sent to the plain resolve endpoint is itself unchanged; only the trigger condition and the reported outcome are new.\n\n**Evidence**\n\n`CCR agent tokens cannot call this route`, `session_route_ccr_denied`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}