## TL;DR

Moved to the threadneedle repo and implemented there: error status codes now map to human-friendly messages instead of the generic "Invalid status code".

## The error

```text
map more error status codes to friendly messages
```

## Fix

1. Moved to the threadneedle repo and implemented there: error status codes now map to human-friendly messages instead of the generic "Invalid status code".
   Expected: You get the expected result; the problem is gone.
2. Re-run the original operation and confirm the error is gone.
   Expected: no error, normal output.

## When to use

- You hit this exact error with Tray.ai.
- The symptom matches: map more error status codes to friendly messages.

## When NOT to use

- A different error message from Tray.ai; the cause here is specific to this error.
- Unrelated Tray.ai issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Tray.ai.

## Variant phrasings

### map more error status codes to friendly messages

## Why it happens

GitHub issue on trayio/falafel: many connector errors surfaced as the unhelpful "Invalid status code"; the request was to map common codes (404 already said "Not found", 429 for rate limits, etc.) to readable messages.

## 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.