AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

resolving-ingestion-warnings

Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Use when a user asks why events are missing, dropped, or undercounted, why identify/alias calls don't work or accounts stay duplicated, why person or group properties aren't updating or profiles look inflated, why recordings have gaps, heatmaps are empty, LLM token counts are missing, why cookieless events vanish, or whenever the `ingestion_warning` health check fires. Explains severity triage (error = dropped, warning = modified, info = intentional) and routes all warning types — size limits and enrichment, merges and distinct IDs, high-volume distinct IDs, `$process_person_profile`, timestamps, cookieless, heatmaps, transformations, session replay — to per-issue reference files with code-level causes and per-SDK fixes.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--resolving-ingestion-warnings at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 17

references/fixing-ignored-invalid-timestamp.md

Fixing ignored_invalid_timestamp

An event's timestamp property couldn't be parsed, so PostHog ingested the event with the server's arrival time instead of the intended one. Category event, severity warning: no event was lost, but its time is wrong — which quietly corrupts trends, funnels with time windows, and historical imports (everything lands at import time).

Note this is strictly about unparseable timestamps. Events that arrive late with valid timestamps (mobile SDKs flushing offline queues, batched backends) are handled normally and don't produce this warning.

What it means in your code

The timestamp string isn't a format PostHog can parse. Common sources:

  • locale formats: "07/08/2026 14:32", "8 Jul 2026",
  • unix epochs sent as strings or in seconds where milliseconds are expected,
  • Date objects serialized via string concatenation instead of .toISOString(),
  • out-of-range values (year 0 or five digits) from arithmetic bugs.

Diagnose

  1. Query the warnings with posthog:execute-sql: SELECT timestamp, details FROM system.ingestion_warnings WHERE type = 'ignored_invalid_timestamp' AND timestamp > now() - INTERVAL 7 DAY ORDER BY timestamp DESC LIMIT 20. The details JSON carries the offending value and a reason from the parser — usually self-explanatory.
  2. Grep the app for where timestamp is set on capture calls (custom timestamps are most common in backend SDKs and migration/import scripts).

Fix

Send ISO 8601 with timezone:

client.capture({
  distinctId,
  event: 'order shipped',
  timestamp: new Date(order.shippedAt).toISOString(), // '2026-07-08T14:32:00.000Z'
})

If you don't need a custom time, omit timestamp entirely — the SDK stamps it correctly. For historical imports, validate the conversion on a sample before running the batch: mis-parsed rows are ingested at "now" and cannot be re-dated afterwards.

Verify

Re-run the flow or a sample of the import, re-query system.ingestion_warnings with posthog:execute-sql (filter type = 'ignored_invalid_timestamp', timestamp after your fix) — no new occurrences — and confirm new events carry the intended times.

Related

  • fixing-event-dropped-too-old.md — the other timestamp-related surprise: valid but old timestamps (e.g. mobile offline queues flushing days later) dropped by a team-configured threshold.