{"version":"2.1.257","anchor":"new-sync-unavailable-outcome-for-livecontainer-sync-conne","canonical_anchor":"new-sync-unavailable-outcome-for-livecontainer-sync-conne","heading":"New 'sync_unavailable' outcome for live\/container sync connections","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-sync-unavailable-outcome-for-livecontainer-sync-conne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New 'sync_unavailable' outcome for live\/container sync connections\n\nLive sync connections recognize a sync-unavailable outcome, handled like other skip reasons for backoff.\n\nLive\/container sync connections now recognize a `sync_unavailable` outcome, meaning the live channel is not available to the session right now. It's handled the same way as the existing `boot_failed` and `ws_open_error` skip reasons for retry\/backoff bookkeeping.\n\n- Area: Artifacts\n- Names: `sync_unavailable`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}