{"version":"2.1.265","anchor":"policyhelpers-entries-gain-a-retries-setting-for-helper-exec","canonical_anchor":"policyhelpers-entries-gain-a-retries-setting-for-helper-exec","heading":"policyHelpers entries gain a retries setting for helper execution failures","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/policyhelpers-entries-gain-a-retries-setting-for-helper-exec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### policyHelpers entries gain a retries setting for helper execution failures\n\nPer-OS `policyHelpers` entries can now set `retries` to control retry attempts after a failed run\n\n**What**\n\nA new `retries` setting on per-OS `policyHelpers.<os>` entries controls how many additional times a failing policy helper (a script that computes managed settings at startup) is retried before it's counted as a failure. A run counts as failed if the helper couldn't launch, exited with a non-zero code, or timed out. Retries use randomized backoff starting at 250ms and doubling up to 4 seconds between attempts.\n\n**Why**\n\nThis gives administrators a way to tolerate transient failures, like a flaky network call inside the helper script, without immediately treating the whole policy helper as failed.\n\n- Area: Managed Settings\n- Names: `retries`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}