{"version":"2.1.232","anchor":"startup-preconnect-is-tracked-per-provider-cache","canonical_anchor":"startup-preconnect-is-tracked-per-provider-cache","heading":"Startup preconnect is tracked per provider cache","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/startup-preconnect-is-tracked-per-provider-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Startup preconnect is tracked per provider cache\n\nThe startup preconnect, skipped for Bedrock and Vertex, is now tracked per provider cache.\n\n**What**\n\nThe one-time preconnect at startup, which is skipped for Bedrock, Vertex, Foundry, Mantle and gateway configurations, now records that it fired on the session's provider cache instead of a process-wide latch, so it resets whenever that cache does.\n\n**Evidence**\n\n`preconnectFired`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}