{"version":"2.1.247","anchor":"not-served-is-now-distinct-from-unavailable-for-session-rela","canonical_anchor":"not-served-is-now-distinct-from-unavailable-for-session-rela","heading":"\"Not served\" is now distinct from \"unavailable\" for session-relayed calls","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/not-served-is-now-distinct-from-unavailable-for-session-rela","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### \"Not served\" is now distinct from \"unavailable\" for session-relayed calls\n\nArtifact and asset calls your session can't relay now report as unsent rather than hard failures.\n\n**What**\n\nCalls that a session's connection declines to carry now report as unsent rather than as a hard failure, across Artifact startup reads, asset uploads\/listing\/deletes, comment resolve and reply, and summon status. Asset access gets a deny message explaining that uploads, listing and deletes are not available from this kind of session.\n\n**Details**\n\n- The new reason is `relay-not-served`, separate from the existing `relay-unavailable`; Artifact startup reads log `boot_relay_not_served`.\n- The HTTP helper gained relay-bound and relay-only delete verbs.\n\n**Evidence**\n\n`relay_not_served`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}