HTTP 429, ingestion

INGEST-004

Ingest rate limit reached.

What it means

Too many batches arrived in the window. Ingestion has its own limiter, separate from sign-in.

What to do

Back off and retry. The recorder does this for you.

The response

Every failure arrives in this shape. The trace_id is worth keeping: it identifies the request in our logs and carries nothing about your data.

{
  "type": "https://shiftgraph.dev/errors/INGEST-004",
  "title": "Ingest rate limit reached.",
  "status": 429,
  "code": "INGEST-004",
  "trace_id": "01J8Z…"
}

Related codes

The endpoint your recorder sends to. The value-free gate lives here: a batch carrying real values is refused rather than stored, and the response names the offending path.

• INGEST-001Unknown ingest key.HTTP 401
• INGEST-002Batch rejected: value-bearing payload.HTTP 422
• INGEST-003Batch exceeds the size limit.HTTP 413

The full error reference, or write to support@shiftgraph.dev with the trace id.