{"version":"2.1.248","anchor":"prewarm-burst-guard-tested-the-wrong-value","canonical_anchor":"prewarm-burst-guard-tested-the-wrong-value","heading":"Prewarm burst guard tested the wrong value","tier":"notice","area":"Session Prewarm","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/prewarm-burst-guard-tested-the-wrong-value","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Prewarm burst guard tested the wrong value\n\nBackground session prewarm now checks the concurrency limit instead of the delay value.\n\n**What**\n\nThe check controlling background session prewarm bursts tested the delay where it meant to test the concurrency limit. The two settings are still fetched remotely, falling back to 15000 ms between bursts and 3 sessions at a time.\n\n**Evidence**\n\n`tengu_bg_prewarm_burst_concurrency`\n\n- Flag `tengu_bg_prewarm_burst_concurrency`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: Session Prewarm\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}