[[["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 details the `BudgetServiceRetryPolicy` class, which is used for handling retries in the `BudgetServiceConnection`."],["The latest release candidate version of the retry policy is 2.37.0-rc, and it includes a list of stable versions going back to 2.11.0, each with its corresponding documentation link."],["Key functions within the `BudgetServiceRetryPolicy` class include `clone()`, `OnFailure(Status const &)`, `IsExhausted() const`, and `IsPermanentFailure(Status const &) const`, which deal with creating new instances, handling failure statuses, and determining retry conditions."],["The document provides detailed parameter and return information for the methods `OnFailure` and `IsPermanentFailure`, indicating that they both accept a `Status const &` parameter and return a boolean value."],["The `BudgetServiceRetryPolicy` is associated with the `BudgetServiceConnection` and is used to determine if operations should be retried, making it a fundamental element for managing communication robustness."]]],[]]
