{"version":"2.1.251","anchor":"auth-retries-and-token-refreshes-no-longer-collide-across-ap","canonical_anchor":"auth-retries-and-token-refreshes-no-longer-collide-across-ap","heading":"Auth retries and token refreshes no longer collide across API hosts","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/auth-retries-and-token-refreshes-no-longer-collide-across-ap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Auth retries and token refreshes no longer collide across API hosts\n\nAuth retries for different API hosts no longer trip over each other.\n\n**What**\n\nThe de-duplication of in-flight 401 retries and token refreshes is now kept per API host instead of in one global map, so concurrent auth work for different hosts no longer interferes.\n\n**Evidence**\n\n`cfe.of(W().host)`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}