Time zones and dates
Distinguish console display time, UTC schedule times, API timestamps, and date variables.
Loading documentation…
Powered by heyo
RestoreTrust stores and exchanges points in time as UTC instants. The console can display those instants in your local time; this does not change when a schedule runs.
Open App settings → Time zone and choose Local time or UTC. Local time is the default and uses the time zone of your browser or device. The choice is saved in that browser, so another browser or teammate can display the same event differently. Absolute timestamps in the console include a short time-zone label, such as MESZ or UTC. Relative labels such as “2 hours ago” describe elapsed time and do not change with this setting.
The setting also controls how the console interprets date-and-time fields: check and report filters and a report's time range use the selected zone. The console converts the entered wall-clock time to an unambiguous UTC instant for the API. The today view starts at midnight in the selected zone; switching zones can therefore change which checks count as today.
| Value | Time zone used | Effect of changing the console setting |
|---|---|---|
| Event, check, report, and worker timestamps | UTC instant, displayed in the selected zone | The displayed clock time changes; the event does not |
| Check/report date-and-time filters and report time range | Entered in the selected zone | The same typed clock time can select a different interval |
| Schedule hour, weekday, and minute window | UTC | No change to the saved cadence |
| Backup path and filename date variables | UTC | No change to file selection |
API-key expiration date (YYYY-MM-DD) | UTC calendar day | No change; the key remains valid through the end of that UTC day |
The hourly, daily, and weekly controls in Schedules describe UTC time, regardless of the console setting. The chosen ten-minute window is resolved to one minute when the schedule is saved. The next-run timestamp is then displayed in your chosen console zone.
For example, a daily schedule saved for 10:10 UTC appears at 12:10 in Berlin during summer time and 11:10 during winter time. It still runs at the same UTC time. If you need a fixed local clock time across daylight-saving changes, review and adjust the UTC schedule when the offset changes.
The {{$yyyy}}, {{$mm}}, and {{$dd}} variables in backup paths and filenames are resolved in UTC. Near local midnight, their date can differ from the date shown in local time. A manual run evaluates those variables for its own run time; inspect the selected artifact on the resulting check.
API responses return timestamps in UTC with a Z suffix and millisecond precision, for example 2026-10-10T10:10:22.316Z. Missing timestamps are null. Timestamp inputs, including list filters, pagination cursors, and report ranges, need an explicit offset or Z; 2026-10-10T12:10:22+02:00 and 2026-10-10T10:10:22Z identify the same instant. A bare clock time or date-only value is rejected for these inputs.
The API accepts a date-only value only where the field explicitly defines a calendar date, such as an API key's expiration. See Requests and responses for the timestamp contract.