{"version":"2.1.236","anchor":"live-watch-tokens-can-be-renewed-in-place-once-the-server-al","canonical_anchor":"live-watch-tokens-can-be-renewed-in-place-once-the-server-al","heading":"Live-watch tokens can be renewed in place, once the server allows it","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/live-watch-tokens-can-be-renewed-in-place-once-the-server-al","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Live-watch tokens can be renewed in place, once the server allows it\n\nLive artifact watches could refresh their connection token in place, but the server never says they can.\n\n**What**\n\nA new call renews the token for an artifact's live update channel instead of tearing down and re-establishing the whole subscription. The client only takes that path when the subscribe response marks the subscription renewable, and nothing in the client sets that field, so the code ships inactive until the artifact service starts returning it.\n\n**Details**\n\n- Renewal posts to `\/api\/frame\/watch-token\/<slug>`; a failure is reported as a renewal miss and the old re-subscribe path is used.\n\n**Evidence**\n\n`watchTokenRenewEnabled`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}