{"version":"2.1.225","anchor":"artifact-comment-errors-distinguish-missing-thread-from-degr","canonical_anchor":"artifact-comment-errors-distinguish-missing-thread-from-degr","heading":"Artifact comment errors distinguish missing thread from degraded fetch","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/artifact-comment-errors-distinguish-missing-thread-from-degr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Artifact comment errors distinguish missing thread from degraded fetch\n\nArtifact comment errors now tell you whether a thread is really missing or just dropped from fetch.\n\n**What**\n\nAsking for an artifact comment thread that is not in the fetched set now says whether the thread genuinely does not exist or whether threads were dropped from the fetch.\n\n**Details**\n\n- Raises `comments_thread_not_found` when the id is absent, with text pointing at the \"comments\" action as the source of thread ids\n- Raises `comments_degraded` instead when threads were dropped, so the model does not conclude the thread is gone\n- A filtered listing that comes back empty now tells the model to re-run without `thread_id`\n\n**Evidence**\n\n`no comment thread ${er} on this artifact \\u2014 thread ids come from action \"comments\"`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}