Last updated · May 2026
- Production-ready APIs
- SOC 2 Type I - In Progress
REQUEST_ID_MISSING
HTTP 4xx with next_step=retry. The server could not resolve a workspace context or request identifier for this call.
What it means
DataVibe attaches a request_id to every call so you and we can trace it across Core, dashboard proxy, and worker. If that pipeline produced no id (typically because a middleware was skipped on a misrouted request) we return this error rather than serving a response that we can't audit later.
How to fix
- Retry the same call once. Most occurrences are transient and the second call gets a fresh request id.
- Confirm you are calling the documented hostnames; private/IP-only paths bypass the request-id middleware.
- If retries keep returning this code, contact support with timestamps and the failing endpoint.