invalid_timestamp

high · Warnings · Documentation

Updated

Browse documentation
On this page

Earlier command and setup reference · Engine 18.6.0rc590 / Reader 8.11.0rc649

What it means

Rows with timestamps that do not match the declared formats were rejected.

What to do: Add the file’s format to timestamp_formats, or fix the export format.

Inspect the rejected representation

Choose a rejected row and compare the original timestamp text with the formats declared by the source contract. A value written as 02/03/2026 needs an unambiguous interpretation before adding a format: accepting it as the wrong day and month is not a repair.

Repair and revalidate

  1. Confirm the source's intended date, clock and timezone conventions.
  2. Add the supported format to timestamp_formats, or correct the export format at its source.
  3. Run observatory validate --config observatory.yaml again and compare the accepted and rejected counts.
  4. Check a previously rejected row's interpreted time before relying on derived durations.

The warning reports refused rows. The analysis covers admitted rows, not every row in the file.