{"version":"2.1.232","anchor":"comment-threads-explain-two-more-reasons-a-resolve-was-refus","canonical_anchor":"comment-threads-explain-two-more-reasons-a-resolve-was-refus","heading":"Comment threads explain two more reasons a resolve was refused","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/comment-threads-explain-two-more-reasons-a-resolve-was-refus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Comment threads explain two more reasons a resolve was refused\n\nRefused comment-thread resolves now name the reason instead of failing generically.\n\n**What**\n\nResolving a comment thread on a published artifact can now report \"not resolved (another user's activation)\" and \"not resolved (unavailable from this session)\" instead of a generic failure, and the resolve request tries a session-scoped route first.\n\n**Details**\n\n- If the session-scoped route returns a 404 that is not a missing-thread error, the request falls back to the older route and records that it fell back.\n- The two new refusals come from server responses: one for a comment raised by a different user's session, and one where the server says the action requires a claude.ai session.\n- The 404 message no longer mentions the artifact being republished.\n\n**Evidence**\n\n`session_route_fell_back`, `not resolved (unavailable from this session)`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}