{"version":"2.1.265","anchor":"artifact-comment-thread-schema-adds-degraded-data-and-scope","canonical_anchor":"artifact-comment-thread-schema-adds-degraded-data-and-scope","heading":"Artifact comment thread schema adds degraded-data and scope-filter fields","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/artifact-comment-thread-schema-adds-degraded-data-and-scope","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact comment thread schema adds degraded-data and scope-filter fields\n\nArtifact comment threads can now report dropped threads and degraded data per thread\n\n**What**\n\nThe data format for artifact comment threads (comment discussions attached to shared artifacts) gained several new optional fields:\n\n- `threads_dropped` and `thread_filter`, which indicate when threads were left out and how the results were filtered\n\n- `scoped_dispatch` and `outside_org`, related to scoping the request\n\n- per-thread flags `resolved_degraded`, `activated_degraded`, `anchor_file_degraded`, and `comments_degraded`, marking when specific parts of a thread's data couldn't be fully loaded\n\n- `anchor_region` and `region_inside`, describing the reference location a thread anchors to\n\n**Why**\n\nThese fields let the client tell the difference between a thread that's simply empty and one where data was dropped, filtered out of scope, or only partially loaded, which should make it clearer when comment data shown is incomplete rather than genuinely absent.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}