{"version":"2.1.259","anchor":"config-lock-acquisition-now-retries-with-backoff-instead-of","canonical_anchor":"config-lock-acquisition-now-retries-with-backoff-instead-of","heading":"Config lock acquisition now retries with backoff instead of failing on ELOCKED","tier":"notice","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/config-lock-acquisition-now-retries-with-backoff-instead-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Config lock acquisition now retries with backoff instead of failing on ELOCKED\n\nSaving or deleting config now retries with backoff when the lock is held instead of failing outright.\n\nSaving or deleting global and project config (`saveGlobalConfig`, `saveCurrentProjectConfig`, `deleteProjectConfig`, `deleteCurrentProjectConfigFields`) now retries lock acquisition with exponential backoff when the config lock is already held, instead of failing outright. Fallback writes skipped or suppressed due to lock contention are now tracked with distinct telemetry, including `tengu_config_fallback_skipped_contention`.\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}