## TL;DR

Catch RateLimitError separately and back off; do not treat it like a bad request.

## Fix

1. Catch RateLimitError separately and back off; do not treat it like a bad request.
   Expected: you can confirm this matches your situation.

## When to use

- You are setting up or using this Reducto Python errors feature.
- The symptom matches: connection vs status vs rate-limit are different exceptions.

## When NOT to use

- Unrelated Reducto Python errors issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Reducto Python errors.

## Variant phrasings

### connection vs status vs rate-limit are different exceptions

## Why it happens

Official package docs (PyPI reductoai): documents a distinct exception hierarchy, 400 BadRequestError, 401 AuthenticationError, 404 NotFoundError, 422 UnprocessableEntityError, 429 RateLimitError, 5xx InternalServerError, plus APIConnectionError for network failures versus APIStatusError for HTTP errors. File inputs accept bytes, path-like objects, or filename plus contents plus media type tuples.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.