[[["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-03-14 UTC."],[[["This webpage details the `UserEventServiceLimitedErrorCountRetryPolicy`, a retry policy for `UserEventServiceConnection` that manages retries based on the count of errors encountered."],["The policy stops retrying if a non-transient error occurs or if the number of transient failures exceeds a predefined limit, with `kUnavailable` being the status code for transient errors."],["The `UserEventServiceLimitedErrorCountRetryPolicy` class provides constructors to create an instance with a specified maximum number of transient errors allowed, and an option to disable the retry loop by setting the maximum failures to 0."],["Key functions include `maximum_failures()`, `OnFailure()`, `IsExhausted()`, `IsPermanentFailure()`, and `clone()`, which respectively provide information on the max failures, whether to retry on failure, if retries are exhausted, if a failure is permanent, and a function to create a new policy instance."],["The webpage provides access to documentation for many different versions of this retry policy, going all the way from version 2.37.0-rc (latest) down to 2.15.1."]]],[]]
