## TL;DR

For groq.NotFoundError: Model not found, Groq retires models, so check the live model list at console.groq.com/docs/models and update the model name in config. For groq.RateLimitError, wait before retrying (check current limits at console.groq.com) or temporarily switch providers.

## The error

```text
groq.RateLimitError, groq.AuthenticationError, groq.NotFoundError fixes
```

## Fix

1. For groq.NotFoundError: Model not found, Groq retires models, so check the live model list at console.groq.com/docs/models and update the model name in config.
   Expected: You see the expected output instead of the problem.
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 Groq.
- The symptom matches: groq.RateLimitError, groq.AuthenticationError, groq.NotFoundError fixes.

## When NOT to use

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

## Compatibility

Reported against Groq. Source: https://github.com/dotdev262/rag-nettwin/blob/HEAD/docs/TROUBLESHOOTING.md.

## Variant phrasings

### groq.RateLimitError, groq.AuthenticationError, groq.NotFoundError fixes

## Why it happens

Three Groq API errors keep recurring in integrations: groq.RateLimitError (Rate limit exceeded), groq.AuthenticationError (Invalid API key), and groq.NotFoundError (Model not found). Each has a distinct fix, and mixing them up wastes debugging time.

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

## Source

https://github.com/dotdev262/rag-nettwin/blob/HEAD/docs/TROUBLESHOOTING.md