ServerOps.ggbeta
GuidesLogsDashboard

Timestamp formats

Every clock format the search bar and the ingest API will accept.

Timestamp formats

Whenever you write a timestamp in SOQL (for example, ts > "2026-05-19T07:00:00Z") or send one in an event body, the same flexible parser handles both surfaces. You do not need to remember the exact format. A handful of common shapes all work.

Accepted formats

All of these resolve to the same moment in UTC:

FormatExampleNote
RFC3339 with Z2026-05-19T07:42:08ZThe canonical ISO format.
RFC3339 with nanos2026-05-19T07:42:08.123456789ZUp to nanosecond precision.
RFC3339 with offset2026-05-19T09:42:08+02:00Converted to UTC.
ISO with no zone2026-05-19T07:42:08Assumed UTC.
Space-separated2026-05-19 07:42:08With or without milliseconds.
Date-only2026-05-19Resolves to midnight UTC that day.
Unix seconds177917652810 to 12 digit integers.
Unix milliseconds177917652800013 or more digit integers.

You can paste any of these into the search bar or send them as the ts field on an event and the system will figure out what you mean.

What is NOT accepted

Slash-separated dates. Formats like 05/19/2026 or 19/05/2026 are rejected. The reason: there is no way to tell whether 05/06/2026 means 5 June or May 6 without knowing the user's locale, and silently picking one would produce months of wrong query results. Use the ISO form 2026-05-19 instead.

Natural language. Phrases like yesterday, last week, or tomorrow at noon are not parsed. The closest thing is the now- relative form:

ts > now-1h
ts > now-30m
ts between now-2d and now-1d

Relative time literals

Inside SOQL, you can use now and now-<duration> directly without quotes:

ts > now-1h        # last hour
ts > now-30m       # last 30 minutes
ts > now-7d        # last 7 days
ts > now-1s        # one second ago

Valid units: s (seconds), m (minutes), h (hours), d (days).

Error messages

If the parser cannot interpret what you typed, the search bar shows a red error panel with three example formats. Pick the one closest to what you meant and try again.

On this page