Times and Timings

This section explains the concept of Times and Timings


Layers, Policies, and Backtests are configured with start and end timings that determine the range of Natural Times that they cover. In addition, Policies are configured with a Schedule Timing, determining when a Policy should run.


Time Ranges

Note that all time ranges in the Myst Platform are end-exclusive. For example, an hourly time range with a start time of 2022-01-01T00:00:00Z and an end time of 2022-01-01T03:00:00Z covers exactly 3 hours.

All Time Series data in the Myst Platform uses interval start time convention. For example, data for the hour 2022-01-01T00:00:00Z to 2022-01-01T01:00:00Z am will have a time of 2022-01-01T00:00:00Z.

Yes Energy uses time end and time start convention depending on the ISO and datatype. All time interval end data is mapped to interval start in the Myst Platform.

Absolute Timing

Absolute Timings specify an exact point in time. They must be specified as an ISO 8601 formatted string in UTC time.

Examples of valid Absolute Timings:

  • 2018-01-01T00:00:00Z indicates January 1st, 2018 at midnight UTC;
  • 2020-05-01T23:00:00Z indicates May 1st, 2020 at 11pm UTC;
  • 2021-08-13T08:00:00Z indicates August 13th, 2021 at 8am UTC.

Relative Timing

Relative Timings specify a point in time that is relative to the As Of Time. They must be specified as an ISO 8601 formatted duration string. See this page for more information on the duration format.

Examples of valid Relative Timings:

  • -P2Y indicates two years in the past;
  • P168H indicates 168 hours into the future;
  • P15D indicates 15 days into the future.

The duration format can also be used to specify a frequency for Schedule Timings. For example, a Schedule Timing of PT1H indicates that a policy should be run every hour.

Cron Timing

Cron Timings specify a point in time based on a cron schedule and can be used to schedule Policies. They must be specified as a cron expression. Users can also specify a time zone when creating a Cron Timing.

Examples of valid Cron Timings:

  • 0 * * * * indicates that a Policy should run every hour;
  • 0 0 * * * indicates that a Policy should run every day;
  • 0 8 * * 1 indicates that a Policy should run every Monday at 8am.

We recommend using Crontab Guru as an editor for cron schedule expressions.