## TL;DR

Set max_completion_tokens to a realistic bound for the task instead of leaving it huge, or the pre-request estimate alone can trigger a 429. Do not code around fixed reset windows, capacity refills continuously.

## Steps

1. Set max_completion_tokens to a realistic bound for the task instead of leaving it huge, or the pre-request estimate alone can trigger a 429. When you get a 429, read which bucket it names: uncached means you need fewer cache misses, total means you need less volume overall. Raise your cache hit rate with prompt caching for repeated instructionss, since cached tokens do not count toward the uncached bucket. Do not code around fixed reset windows, capacity refills continuously.

## When to use

You are seeing this: When you get a 429, read which bucket it names: uncached means you need fewer cache misses, total means you need less volume overall. Use this skill when you run into "Cerebras rate limits: dual uncached/total token buckets, 429 names the bucket".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
