Time rules in config specs
Time rules in config specs are not absolute. The version selected by a time rule can change after an update packet is imported at your replica.
For example, your config spec has the following time rule, which selects
the latest version on the main branch as of July 10 at 7:00 p.m.:
element /vobs/dev/plan.txt /main/LATEST –time 10-Jul.19:00
When you put this rule in the config spec, the latest version on the main branch was 17. However, a developer at another replica created version 18 on July 10 at 6:00 p.m. your time, but this change has not been propagated to your replica. After the update packet that contains the change is imported at your replica, your time rule selects version 18.