Skip to content

TimeStamp

The Time Stamp operation captures the current time and emits it in two forms: a raw nanosecond timestamp and a formatted string in a selected timezone. It is primarily used to annotate events with the moment they were processed.

Time Stamp operation

Inputs

PortTypeRequiredDescription
CreateAnyYesFires the stamp. The value is ignored — any value, including false or Nil, produces a timestamp. This port is not a gate: TimeStamp answers with the moment it ran, so there is nothing for a value to gate on.

Outputs

PortTypeDefaultDescription
TimeStamp(ns)IntegerNilNanosecond timestamp at the moment of execution.
TimeStamp(TZ)StringNilFormatted timestamp in the configured timezone. ISO-8601 with milliseconds and numeric offset (e.g. 2025-09-28T10:23:45.123+01:00).

Properties

NameTypeDefaultDescription
TimeStamp TimezoneTimeZoneLocal timezoneTimezone used to format the TimeStamp(TZ) output string.
On ErrorComboStop this branchPer-op On Error verb (Stop this branch / Continue with the last value / Continue with the fallback). See the Error Handling guide.

State on Reload

Outputs are preserved across restarts when stored state is available. Saved state is discarded if the configured TimeStamp Timezone changed (the formatted string output is timezone-specific).


  1. Gate check — Evaluate the Gate input. A false or Nil value stops the execution path; outputs retain their previous values and downstream operations are not triggered.

  2. Capture time — Record the current time as nanoseconds since epoch.

  3. Format — Convert the nanosecond timestamp to an ISO-8601 string using the configured timezone.

  4. Output — Emit both TimeStamp(ns) and TimeStamp(TZ).


Gate: true   TimeStamp Timezone: Europe/London

TimeStamp(ns): 1727518425123000000

TimeStamp(TZ): "2025-09-28T10:23:45.123+01:00"


  • Annotating sensor readings or events with precise timestamps.
  • Recording the exact time an execution path was triggered.
  • Providing timezone-aware formatted times for logging or display.

  • The gate input is mandatory in the schema; timestamps are only generated when the gate allows execution.
  • Timezone must be valid; an invalid timezone will prevent proper formatting.