A valid-looking clock entry can have no instant
On 8 March 2026 in New York, the clock advances from the pre-change hour into the next one, skipping the local 02:00 hour. The entry 02:30 on that date has no matching instant in America/New_York. It is not a second interpretation of the same event; the requested wall time never occurs under those rules.
Correct the instruction deliberately
Choose a local time that exists and confirm the new result with the participants. In this example, changing the input to 03:00 New York resolves to 07:00 UTC. That is a new, explicit meeting instruction. A silent adjustment would hide the difference between the time the user asked for and the time that was scheduled.
If the intended meeting was specified by an absolute UTC timestamp, enter that instant through a valid base-time conversion instead. It may display on the other side of the skipped hour. Distinguish that case from an organizer who explicitly requested a nonexistent local wall time.
A recurrence can skip an occurrence when you choose
For a weekly plan, you may decide that the affected meeting should not happen. Mark that occurrence as skipped explicitly and inspect the revised event count. The other reviewed weeks retain their anchor-city local instruction. A skipped row must not turn into an event quietly shifted into a different hour.
A schedule change may be preferable to a skip. If you move the weekly anchor time, review the whole preview again: the correction affects the planning instruction, not just the label in one table cell. Check the other cities’ availability after the change.
Keep export blocked until the plan is resolved
An ICS event needs a real start and end. A missing local time does not supply them. Correct or skip the affected occurrence before downloading, and compare the expected number of events after import. Keep the project JSON if you want to retain the editable decisions.
Use the zone and data version in a report
When investigating a missing-time warning, record the exact date, clock time, IANA identifier, and rule version. A nearby city or a different year may have different behavior. The planner supports 2026–2035 with its bundled IANA 2026f rules, so dates outside that range require a different verified data set.
Sources
Follow the original references for the rules and formats used in this guide.