Exponential-backoff retry for transient server-side failures (502,
503, 504 — see isTransientServerError). Wraps the attempt
with withRetryBackoff using the caller-provided telemetry
hook for every retry tick.
This policy only makes sense on idempotent verbs (typically GET):
retrying a POST that may have landed server-side is a duplicate
write in disguise. The consuming client gates application of this
policy accordingly; the policy itself is neutral about method.
Ownership: transient 5xx. Non-transient 5xx (e.g., 500) or any
other error propagates untouched on the first failure — no retry.
Exponential-backoff retry for transient server-side failures (502, 503, 504 — see isTransientServerError). Wraps the attempt with withRetryBackoff using the caller-provided telemetry hook for every retry tick.
This policy only makes sense on idempotent verbs (typically GET): retrying a POST that may have landed server-side is a duplicate write in disguise. The consuming client gates application of this policy accordingly; the policy itself is neutral about method.
Ownership: transient 5xx. Non-transient 5xx (e.g., 500) or any other error propagates untouched on the first failure — no retry.