{"version":"2.1.227","anchor":"sync-stops-itself-after-repeated-auth-refusals-repeated-cras","canonical_anchor":"sync-stops-itself-after-repeated-auth-refusals-repeated-cras","heading":"Sync stops itself after repeated auth refusals, repeated crashes, or a rehomed workspace","tier":"notice","area":"Remote Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/sync-stops-itself-after-repeated-auth-refusals-repeated-cras","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Sync stops itself after repeated auth refusals, repeated crashes, or a rehomed workspace\n\nWorker syncing shuts itself off after repeated auth failures, crashes or a moved workspace.\n\n**What**\n\nRather than retrying forever, the worker syncer turns itself off on three conditions and the session continues without syncing.\n\n**Details**\n\n- `MAX_CONSECUTIVE_AUTH_REFUSALS` (10) consecutive auth refusals, or a single response saying the session is refused, disarms it with a `dir_sync_worker_session_refused` warning.\n- `MAX_CONSECUTIVE_PHASE_CRASHES` (3) unexpected exceptions in a pull or push phase also disarms it; each crash logs `dir_sync_worker_phase_crashed` with the error name, error code and consecutive count.\n- If a resumed worker finds itself pointed at a workspace that already has a non-empty published record from someone else, it logs `dir_sync_worker_rehomed_disarmed` and stops rather than merging the two.\n\n**Evidence**\n\n`dir_sync_worker_rehomed_disarmed`\n\n- Area: Remote Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}