[[["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 document provides information on the `TraceServiceLimitedErrorCountRetryPolicy`, a class used for controlling retries in the `TraceServiceConnection` based on error counts."],["The retry policy halts when a non-transient error occurs or when the number of transient failures exceeds a predefined limit, with `kUnavailable` as a recognized transient error code."],["Users can customize the retry behavior by setting the `maximum_failures` parameter during policy instantiation, and can disable the retry loop by setting it to 0."],["The document lists versions ranging from 2.11.0 to 2.37.0-rc for the `TraceServiceLimitedErrorCountRetryPolicy` class."],["The policy offers various functions, including `maximum_failures()`, `OnFailure()`, `IsExhausted()`, `IsPermanentFailure()`, and `clone()` to manage and assess retry attempts and failures."]]],[]]
