Rule chains: conditions and expressions can use now, the current time in milliseconds, with the units second, minute, hour and day. For example, data.timestamp > now - 5 * minute passes only for a write made in the last five minutes.
Rule chains: a chain triggered by a data change receives data.previous, the value and write time of the field before this change, so a chain can compare the new value with the old one.
Rule chains: every run receives data.local, the run's time in the platform's time zone: year, month, day, hour, minute, second, weekday, the zone name and its offset. Daylight saving changes follow the zone's own rules, with nothing to configure in the chain.
Rule chains: a Read node also returns when each field it reads was last written, as the field's key followed by WrittenAt.
Rule chains: a Time Condition node checks its time ranges against the platform's local time instead of UTC.
Rule Chain Editor: a new On Schedule trigger starts in the platform's time zone, and the trigger's outputs list previous and local so they can be picked in later nodes.
Notes
Rule chains: a chain that runs once when armed skips that first run if it uses now or the previous value, since neither has a meaning before the first change. It runs on the next change as usual.