[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThis webpage details the \u003ccode\u003eDataFusionLimitedErrorCountRetryPolicy\u003c/code\u003e, a retry mechanism for \u003ccode\u003eDataFusionConnection\u003c/code\u003e that limits retries based on the number of errors encountered.\u003c/p\u003e\n"],["\u003cp\u003eThe policy halts retries when it encounters a non-transient error or when the number of transient errors exceeds a predefined limit.\u003c/p\u003e\n"],["\u003cp\u003eOnly \u003ccode\u003ekUnavailable\u003c/code\u003e status codes are considered transient errors, triggering a potential retry.\u003c/p\u003e\n"],["\u003cp\u003eThe policy can be configured to disable retries entirely by setting \u003ccode\u003emaximum_failures\u003c/code\u003e to 0, and it has multiple constructors and functions, such as \u003ccode\u003eOnFailure\u003c/code\u003e, \u003ccode\u003eIsExhausted\u003c/code\u003e, and \u003ccode\u003eclone\u003c/code\u003e, to manage retries.\u003c/p\u003e\n"],["\u003cp\u003eThe webpage offers documentation on the retry policy, spanning from version 2.13.0 up to the latest release candidate, 2.37.0-rc.\u003c/p\u003e\n"]]],[],null,[]]
