[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-23 UTC."],[[["This document outlines the `SystemPolicyV1LimitedErrorCountRetryPolicy`, which is designed to manage retries for `SystemPolicyV1Connection` based on the number of errors encountered."],["The policy stops retrying if a non-transient error occurs or if the number of transient failures exceeds a predefined limit, and `kUnavailable` status codes are considered transient errors."],["The class offers constructors to set the maximum number of transient errors (`maximum_failures`) and methods such as `maximum_failures()`, `OnFailure()`, `IsExhausted()`, `IsPermanentFailure()`, and `clone()` for managing and assessing the retry state."],["The retry loop can be fully disabled by instantiating the policy with `maximum_failures` set to 0."],["There are currently 27 versions of this policy ranging from version 2.11.0 up until the most current at 2.37.0-rc."]]],[]]
