We've decided to make less money: We've slashed our pricing for session replay. They're now more than 50% cheaper for most customers.

Ingestion warnings

Last updated:

|Edit this page

Sometimes PostHog runs into problems during ingestion due to incorrect or suboptimal usage of PostHog. For example, if you capture an event with a generic ID like null, PostHog doesn't ingest it.

If this happens, we do our best to still ingest the event and we log an ingestion warning.

Ingestion warnings

Note: These warnings are sampled. The actual number of events affected may exceed the total displayed.

List of ingestion warnings:

Refused to merge with an illegal distinct ID

See our identify docs for what happens when you call identify or alias with an illegal distinct ID like guest or null.

Refused to merge an already identified user

See our identify docs for details on how we handle duplicate users.

Refused to process event with invalid UUID

PostHog drops events with invalid UUIDs.

There are very few cases where it would be good to provide an event UUID. PostHog generates these for you.

When generating UUIDs, there are many gotchas to be aware of. For example, deduping based on event UUID is not guaranteed due to how merges work in ClickHouse.

Ignored an invalid timestamp, event was still ingested

When capturing events, the timestamp and sent_at fields should be in ISO 8601 format. When parsing fails, PostHog ignores these fields and computes them itself as if omitted. These events are still ingested, but their timestamp might be different than the one you intended.

An event was sent more than 23 hours in the future

This warning indicates a bug in your instrumentation, as we don't expect events from the future. Read about how we compute event timestamps and review your instrumentation code (the sent_at or the offset values might be wrong).

These events are ingested and stored, but will not show up in the UI. If these events create new persons, these persons will have a "first seen" property in the future.

Discarded event exceeding 1MB limit

PostHog discards events exceeding 1 megabyte in size after processing. The two common ways this happens are:

  1. An event is captured with an exceptionally large number of properties (including person properties)

  2. One or more installed apps transformed the event and enriched it with a large amount of additional property data.

Event ingestion has overflowed capacity

This warning indicates PostHog is receiving more events for a single distinct_id than it can process in the main ingestion pipeline. These events are still safe and ingested but through a slower overflow pipeline. This is often a sign of an instrumentation bug such as a loop sending the same event.


Was this page useful?

Next article


People in PostHog represent the users behind your events. You can view them in the People tab . People have person properties , which enables you do things like: Filter on person properties Create cohorts Use person properties for targeting feature flags, A/B tests, and surveys. Track initial UTM values and referrers across anonymous and identified users. Query the persons table using SQL insights People and person profiles Using people in PostHog requires capturing events with person…

Read next article