주제: retries
-
Honor Retry-After as a lower bound
Schedule retries from either form of Retry-After while preserving the task deadline and avoiding premature repeated requests.
-
Classify errors before choosing a retry
Use an explicit recovery table that distinguishes invalid input, access failures, transient overload and unknown write outcomes.
기계 판독 가능: JSON