Recognize the missing-time state
A forward clock change can skip a range of wall-clock labels. If your selected date and time falls in that gap, the app reports that the local time does not exist. There is no valid instant to convert or export until you change the instruction.
Use a real replacement
For New York on 8 March 2026, 02:30 is missing. Change the input to a valid local time, such as 03:00, and inspect the resulting 07:00 UTC instant. This is an explicit replacement, so confirm it with the participants. The app does not silently move 02:30 to another hour.
Handle the occurrence in a weekly preview
For a recurring plan, choose to correct the affected occurrence’s local time or explicitly skip it. A skip removes that occurrence from the export count while keeping the other reviewed dates. The skip policy must be chosen deliberately; an unresolved missing row keeps the series download unavailable.
Check the rest of the meeting
After correcting the start, review every city’s local date, end time, and availability. A valid replacement can still be outside a participant’s working hours. Changing the series-wide anchor time affects more than the one problematic row, so recheck all twelve occurrences if you edit the general instruction.
Download only the resolved events
The calendar summary should agree with the number of resolved, unskipped rows. If twelve rows include one intentional skip, the file contains eleven events. Import the file and confirm that the skipped date did not appear as an automatically shifted event.
If the warning surprises you
Verify the year, date, local time, and exact IANA identifier. A neighboring city may have different rules. Record the displayed data version if you investigate further. The bundled range is 2026–2035; an out-of-range date is a separate problem and should not be treated as a missing-time correction.
Sources
Follow the original references for the rules and formats used in this guide.