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.llama-3.3-70b-versatile in organization org_01kxd8hjn4f7vtzgf55x2e48x9 service tier on_demand on tokens per minute (TPM): Limit 12000, Requested 35421, please reduce your message size and try again. Need more tokens? Upgrade to Dev Tier today at console.groq.com/settings/billingllama-3.3-70b-versatile in organization org_01kxd8hjn4f7vtzgf55x2e48x9 service tier on_demand on tokens per minute (TPM): Limit 12000, Requested 35421, please reduce your message size and try again. Need more tokens? Upgrade to Dev Tier today at console.groq.com/settings/billing",archestra__run_command to write files. Problem with that is that I always hit a Error: command is too large (> 16384 bytes) error, and it forces the agent to unreliably find workarounds (once it tried rewriting the HTML file in small splits, forcing the content to be rewritten in small pages and links between them, another time it just zipped everything). I got the same when working with Apps, even more brutally given that, well, it’s all about apps. Is my agent misconfigured or is this a current limitation of Archestra?context_too_longRequest too large for model llama-3.1-8b-instant. Requested 40280 tokens.Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!