Errors
500 - internal server error
What happened
The service failed while handling the request. A write may have an unknown outcome if the failure happened after it was accepted.
- Keep the error detailsRecord the trace ID and time without secrets.
- Check the stored stateDetermine whether an attempted write already took effect.
- Choose the next actionBound read retries; reconcile writes or contact support.
- Verify the outcomeConfirm the intended state rather than only the HTTP status.
Request that triggers it
Any normally-valid request that surfaces a bug or unhandled internal condition.
curl -X POST "https://$OC_HOST/v1/tenants/$OC_TENANT/sql" \
-H "Authorization: Bearer $OC_TOKEN" \
-H "Content-Type: application/json" \
-d '{"sql": "SELECT id FROM shop.products LIMIT 1"}'Read the response
{
"error": "internal_error",
"message": "unexpected backend error; please retry. If this persists, contact support with the trace id below.",
"retry": true,
"trace_id": "0b1c2d3e-4f50-6172-8390-a1b2c3d4e5f6",
"status_page": "https://status.originchain.ai"
}Fix the request
- Keep the request or trace ID and time.
- For a read, use bounded backoff.
- For a write, check the stored result before repeating it.
- Contact support with non-secret diagnostics if the failure persists.
Keep in mind: A server error does not prove that a write was rolled back. A fresh idempotency key alone does not make replay safe.
Common causes
- A new bug surfaced by a recent deploy.
- The engine running out of memory while handling a large query.
- A storage read or write failure.
- An unexpected internal failure; the trace ID helps support locate it.
- An internal dependency (the platform or billing service) was momentarily down.
Continue
See error handling and retries, or return to error examples.