Archestra Apps HackathonSee what people are building

Thread

HI
harshal ingle10:17 AMOpen in Slack
Hi,
Sharing two exact errors I hit today building on Archestra: with *Cerebras, a model call failed with Status: 402, Type: unknown_api_error, Message: "402 status code (no body)" โ€” no further detail in the response. With Groq* (Llama 3.3 70B), even in a fresh chat with a short prompt, I got Status: 413, Type: api_payload_too_large_error, Message: "Request body too large: 0.0 MB (limit 70 MB). Use a smaller attachment, or raise ARCHESTRA_API_BODY_LIMIT." โ€” the reported size (0.0 MB) doesn't match the "too large" error. Posting in case others have hit the same and can point to a cause โ€” happy to share full raw JSON for either if useful.

1 reply
A
Archestra10:17 AMOpen in Slack
Hi Harshal! Thanks for the detailed report. *Cerebras 402: This typically means a billing/quota issue on the Cerebras side โ€” their API returned a payment-required status with no body. Worth checking your Cerebras account credits or API key permissions. Groq 413 with "0.0 MB": That's a weird one โ€” the size mismatch suggests the error message isn't being populated correctly. Could be a bug in how the error is constructed. Let me check if there's anything in the codebase or recent issues about these. Can't search the codebase right now, but here's my take: - Cerebras 402 โ€” definitely upstream, not Archestra. Check your Cerebras dashboard for credits/billing status. - Groq 413 "0.0 MB"* โ€” this looks like a bug worth reporting. The error message formatting is off. Could you open an issue at https://github.com/archestra-ai/archestra/issues with the raw JSON? That'd help the team debug. Anyone else seen these? ๐Ÿค– Slack Agent