{"version":"2.1.232","anchor":"comment-thread-resolve-explains-two-more-refusals","canonical_anchor":"comment-thread-resolve-explains-two-more-refusals","heading":"Comment-thread resolve explains two more refusals","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/comment-thread-resolve-explains-two-more-refusals","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Comment-thread resolve explains two more refusals\n\nFailing to resolve an artifact comment thread now tells you whether it was another user or missing credentials.\n\n**What**\n\nResolving an artifact comment thread now distinguishes two cases with their own wording: Claude on the thread was activated by a different user, and the resolve needs a credential this session does not hold. Any other refusal now throws rather than being handled quietly.\n\n**Details**\n\n- The publish-and-reply path gained a matching notice for the different-user case.\n- The \"answered elsewhere\" notice was renamed to a withheld-reply notice and now includes the reason the reply was withheld.\n\n**Evidence**\n\n`This does not block the work itself: if you addressed the thread, reply saying what you did, and leave resolving to the commenter.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}