Skip to main content
When encountering runtime exceptions or deployment warnings on the Karada platform, use this reference index to identify root causes and implement fixes.

​
Build & Deployment Errors

​
ERR_BUILD_FAILED

The isolated container sandbox failed during the compilation or packaging phase.
  • Root Cause: Missing dependency in manifest, syntax error in custom code modifications, or incompatible runtime version.
  • Resolution: Check the real-time Deployment Logs in your project dashboard. Verify your dependencies and build commands match production requirements.

​
ERR_SANDBOX_TIMEOUT

The container failed to initialize or bind to the assigned port within the startup threshold.
  • Root Cause: Server blocked on an unreachable database or crashed immediately on startup without logging to stdout.
  • Resolution: Confirm your server listens on the port defined by the PORT environment variable and handles graceful startup without blocking health checks.

​
Auto-MCP Specification Errors

​
ERR_INVALID_OPENAPI

Karada’s ingestion engine was unable to parse the provided API specification document.
  • Root Cause: The URL returned an HTML error page, JSON/YAML syntax was malformed, or the schema used an unsupported format.
  • Resolution: Validate your specification using Swagger Editor. Karada natively supports OpenAPI v3 (.json / .yaml) and Swagger v2 (.json / .yaml).

​
ERR_MISSING_TOOL_DESCRIPTION

An extracted endpoint could not be mapped to a clean LLM tool.
  • Root Cause: An API path in your spec lacks both summary and description annotations. LLMs require natural language descriptions to perform tool selection.
  • Resolution: Add concise summary strings to each route in your OpenAPI definition and re-generate your server.

​
Connection & Gateway Errors

​
ERR_AUTH_REJECTED

The upstream API rejected the request proxied by Karada.
  • Root Cause: Missing, invalid, or expired API key or Bearer token.
  • Resolution: Verify your credentials under Project Settings → Environment Variables (or in the Gateway Secret Vault) and confirm the token has required upstream scopes.

​
ERR_MCP_PROTOCOL_VIOLATION

The AI client (Claude Desktop, Cursor) could not establish or maintain JSON-RPC communication with the MCP server.
  • Root Cause: Network proxy stripped required streaming headers, or client configuration URL lacked the /sse suffix.
  • Resolution: Ensure your AI client configuration points to the exact streaming URL (e.g., https://<project-slug>.karada.ai/sse).
[!TIP] Encountering an unlisted error? Connect directly with the engineering team on the Karada Discord or submit a report to shashtag-ventures/karada-docs.