{"version":"2.1.242","anchor":"artifact-comment-reading-now-sits-behind-a-server-side-switc","canonical_anchor":"artifact-comment-reading-now-sits-behind-a-server-side-switc","heading":"Artifact comment reading now sits behind a server-side switch","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/artifact-comment-reading-now-sits-behind-a-server-side-switc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Artifact comment reading now sits behind a server-side switch\n\nReading artifact comments is now behind a server switch that is off, so nothing is fetched.\n\n**What**\n\nReading comments on an Artifact is gated on `tengu_onyx_sluice`, which falls back to off in this build. With it off nothing is fetched at all and you get \"comments are not available on this artifact right now\", counted as `cp_read_disabled`. With it on, transport errors and HTTP 5xx or 499 are retried once after a random backoff and the unavailable message includes the HTTP status.\n\n**Details**\n\n- Retries are reported as `server_read_retried`.\n- The old path that fetched comment JSON directly from the content host is gone, along with its `__frame_t` and `json_egress_blocked` handling.\n\n**Evidence**\n\n`cp_read_disabled`\n\n- Flag `tengu_onyx_sluice`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.242; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}