{"version":"2.1.257","anchor":"artifact-live-subscribe-gains-a-second-non-websocket-sync","canonical_anchor":"artifact-live-subscribe-gains-a-second-non-websocket-sync","heading":"Artifact live-subscribe gains a second, non-websocket \"sync\" transport","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/artifact-live-subscribe-gains-a-second-non-websocket-sync","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Artifact live-subscribe gains a second, non-websocket \"sync\" transport\n\nLive artifact connections can use a new sync transport alongside websockets, with its own keepalive and reconnect logic.\n\nThe artifact-watch supervisor that keeps a live connection open on a published artifact for auto-reply\/reconnect logic can now open either the old websocket transport or a new `sync` transport, which has its own URL builder, dedicated ping-frame keepalive, and 404\/expiry-based reconnect detection. Telemetry marks these connections with `sync_transport: true` in the `artifact_live_subscribe` event. The live-subscription bootstrap logic now distinguishes a lease's transport as `live` or `sync`, validates sync leases against stored credentials, and returns a new `sync_unavailable` outcome when sync can't be established.\n\n- Area: Artifacts\n- Names: `sync_transport`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}