{"version":"2.1.275","anchor":"kept-reminderidle-probe-renamed-to-threads-probe-with-its-o","canonical_anchor":"kept-reminderidle-probe-renamed-to-threads-probe-with-its-o","heading":"Kept-reminder\/idle probe renamed to threads probe with its own failure counter","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/kept-reminderidle-probe-renamed-to-threads-probe-with-its-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Kept-reminder\/idle probe renamed to threads probe with its own failure counter\n\nThe idle\/kept-reminder probe is now a 'threads probe' with its own failure counter separate from the existing one\n\n**What**\n\nAn internal background probe, previously tied to kept-reminder\/idle checks, is now referred to as a threads probe and tracks its own consecutive-failure count via a new `threadsProbeFailures` counter, giving up after 2 failures. This is separate from the existing `clearAtProbeFailures` counter used elsewhere.\n\n**Why**\n\nSeparating the failure tracking lets this probe fail and back off independently without affecting the other probe's failure count.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}