{"version":"2.1.247","anchor":"artifact-relay-skips-bot-driven-sessions","canonical_anchor":"artifact-relay-skips-bot-driven-sessions","heading":"Artifact relay skips bot-driven sessions","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-relay-skips-bot-driven-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact relay skips bot-driven sessions\n\nBot-driven sessions no longer relay artifact requests; they go direct or not at all.\n\n**What**\n\nWhen the session is a bot context, the code that decides how to reach the artifact service stops before relaying: it records `bot_context_not_served` once and returns either not-served or direct instead.\n\n**Details**\n\n- The helper that picks the relay leg now takes a mode of `\"fallback\"`, `\"bound\"` or `\"only\"` in place of a boolean.\n- A separate new predicate combines hosted session, bot context and the new flag `tengu_cobalt_plinth_fennel`, whose compiled fallback is off. The neighbouring relay flags `tengu_cobalt_plinth_sorrel` and `tengu_cobalt_plinth_madder` fall back to on.\n- The old boolean-argument helper was renamed and kept.\n\n**Evidence**\n\n`bot_context_not_served`\n\n- Flag `tengu_cobalt_plinth_fennel`: Off in both readings (read for one account on one subscription tier against v2.1.247; this account: off, anonymous baseline: off, compiled default: not a boolean we can read)\n- Flag `tengu_cobalt_plinth_sorrel`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.247; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Flag `tengu_cobalt_plinth_madder`: Off in both readings (read for one account on one subscription tier against v2.1.247; this account: off, anonymous baseline: off, compiled default: not a boolean we can read)\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}