Skip to main content
Most issues fall into a handful of buckets. Find the symptom below; each points at the cause and the fix. For the full list of status codes, see the errors reference.
We support the platform - deploys, keys, budgets, sessions, the dashboard. Debugging your agent’s own logic, prompts, or model output is yours to own, and we’ll gladly help you tell the two apart.

​
A deploy is stuck or failed

  • Build failed. Check the release’s build logs in the dashboard. A failed build never replaces the running release - your last good release keeps serving.
  • Deploy succeeded but the app 409s with “no active release”: the project has no materialized release yet. Re-run the deploy; see Deploy loop and Releases & rollback.
  • A new release misbehaves. Roll back to the previous release from the dashboard - rollback is instant and does not rebuild.

​
401 Unauthorized

Your API key is missing, wrong, or revoked.
  • Keys are shown once at creation and stored as a prefix/last-4 afterward - if you lost it, rotate a new one rather than hunting for the old.
  • Confirm you’re sending it as a Bearer token. See Authentication.
  • A revoked or rotated key fails closed immediately.

​
402 Budget exhausted

A budget cap was hit. Karta checks the cap before running anything, so you get a clean 402 instead of a surprise bill.
  • Raise or adjust the cap in Usage & budgets, or wait for the period to reset.
  • A just-raised cap can take a few seconds to propagate (the data plane caches the budget decision briefly). See Usage, cost & budgets.

​
A model call fails (BYOK)

If you bring your own model key, a model error usually means the key is invalid, expired, or out of quota with your provider.
  • Re-check the key in BYOK settings; rotate it if your provider rotated it.
  • Without BYOK, model inference is billed through Karta and you won’t hit this. See Bring your own key.

​
404 on a session

Sessions are org- and project-scoped, default-deny.
  • A session created under a different project (or org) returns 404 by design - it’s not leaked across tenants.
  • Check you’re using a session token scoped to the right project. See Sessions and Session tokens.

​
A webhook endpoint went quiet

  • Karta auto-disables an endpoint after repeated consecutive failures so a dead destination doesn’t back up the queue. Fix the destination, then re-enable it in the dashboard.
  • Deliveries are retried with backoff; check the endpoint’s recent delivery attempts. See Webhooks.

​
429 Too Many Requests

You hit a rate limit. Back off and retry with exponential backoff; sustained limits mean you should batch or spread the load.

​
Is it me, or is Karta down?

Check the status page - it shows live data-plane, Stripe, and database health, and during an incident we post updates there. The status pill in your dashboard footer links to it.

​
Still stuck? Report a problem

  • From the dashboard: use Report a problem in the footer - it reaches the support team with your org and the page you were on already attached.
  • Email: [email protected] for product and account help.
  • Security vulnerability: follow the security policy (coordinated disclosure + safe harbor).
  • Abuse or a leaked key: report abuse - no account required.
  • Privacy / data requests: [email protected]. Legal / DMCA: [email protected].