Skip to content
Start free
Menu
TraceLog is rejecting events

TraceLog is rejecting events

Events sent for this project are reaching TraceLog and coming back refused, each with its reason. Read the reason to find what to correct in the request.

What was observed

TraceLog refused events sent for this project, or the code in the verification tab reported that TraceLog rejected its requests. This row carries the reason with it, so you can see which part of the request was wrong.

Check the event delivery response and correct the rejected request before trying again.

The reasons TraceLog gives

ReasonWhat it means
invalid_schemaA field is missing, misspelled, or the wrong type
unknown_versionThe envelope version is one this API does not know
too_largeThe batch exceeded 256 KB, or carried more than 50 events
future_timeAn event's occurredAt was more than five minutes ahead of the server's clock
expiredAn event's occurredAt falls on a day TraceLog no longer keeps, more than 30 days back; never raises this row

Events more than seven days old are accepted and marked as late. An event from a day more than 30 days back is refused on its own, as expired, and the rest of its batch is stored.

What to check

  1. Read the rejection reason on Installation or Data health — it names the condition and keeps the last example.
  2. invalid_schema on a server-side call is usually the event name form (lowercase, starting with a letter), occurredAt without millisecond precision, or an eventId or sessionId that is not a UUID v7. A context over 8 KB serialised is invalid_schema too.
  3. future_time means a clock is wrong, usually on the sending machine rather than on the event.
  4. too_large means the batch itself was over 256 KB or held more than 50 events: send smaller batches.
  5. expired appears in the server API's response, not in this row. Something held the event for over a month before sending it — a replay, or a queue that waited that long. Nothing to fix in the installation; send recent events.

Effect on verification

It reports. Refused events are not stored, so they cannot count towards verification.