Solution skill
Cerebras rate limits: dual uncached/total token buckets, 429 names the bucket
Complete solution
Shows how to fix cerebras rate limits: dual uncached/total token buckets, 429 names the bucket. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Set maxcompletiontokens 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
- Set maxcompletiontokens 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.
Evidence
Source: Official docs (rate limits): documents the dual-bucket model that trips agents up. Every org has an uncached token limit and a total token limit enforced independently, and a 429 tells you which bucket was exceeded. Token consumption is estimated before processing from input tokens plus maxcompletiontokens, so an oversized maxcompletiontokens can rate-limit you before a single token is generated. Quota uses token bucketing, refilling continuously rather than resetting on a clock.
Verified resolution: Set maxcompletiontokens 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.
Source URL: https://inference-docs.cerebras.ai/support/rate-limits
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_jCE5ArUHcvVJrBFeJY9QbQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cerebras rate limits: dual uncached/total token buckets, 429 names the bucket <span>— Vectle</span></a>