UBER-EATS-Wrapper/docs/developer-portal/09-errors-guide-audit.md

36 lines
901 B
Markdown

# 09 Errors Guide Audit
Source checked: Uber Eats "Errors" section shared by you.
## Implemented Now
- Centralized Uber error normalization with:
- HTTP status
- platform/error code
- transient classification
- raw upstream details
- Safe retry strategy implemented in proxy/auth/reporting calls:
- retries only transient failures
- exponential backoff with jitter
- max 4 attempts
- Global API error response now returns:
- `code`
- `transient`
- `message`
- `requestId`
## Retry Classification Used
- Retryable:
- `408`, `429`, `502`, `503`, `504`
- network timeout/connectivity/reset failures
- Non-retryable by default:
- validation/auth/resource conflict 4xx responses
- `500` (unless network failure classification applies)
## Pending
- Per-endpoint custom retry budgets for high-impact operations
- Circuit-breaker layer for prolonged upstream instability