Practical guide
Recurring Clock Gaps and Repeats: Apply the Verified iCalendar Correction
A weekly local start can fall in a clock gap or a repeated interval. Use verified RFC 5545 erratum 4271 to interpret the instant, then compare two complete fictional COUNT=3 schedules.
On this page
Keep the recurring clock, zone and instant together
A local clock reading can be absent when a clock moves forward, or can occur twice when it moves back. A timed recurrence that says 02:30 therefore needs more than a list of dates. You need its timezone definition, the occurrence’s nominal local start and the rule that selects its actual instant. [1]
The original practice zone here is Example/Clock-2027. It is fictional, with explicitly supplied offsets, and does not represent a city or an IANA zone. At March 14 2027 02:00, its clock moves from +0000 to +0100 and reads 03:00. At November 7 03:00, it moves from +0100 to +0000 and reads 02:00. These definitions create a 02:00–03:00 gap in March and a repeated 02:00–03:00 interval in November.
Both specimens recur weekly at nominal 02:30, starting on a Sunday, with COUNT=3. One starts March 7; the other October 31. All dates and UIDs are fictional practice data. The two complete files below contain the finite zone definition and one transparent 30-minute VEVENT each; their displayed end or calendar import behavior has not been tested.
The existing 09:00 local-versus-UTC recurrence guide covers ordinary starts outside the overnight transition intervals. This guide answers the separate question of what an actual gap or repeated start means. Floating travel routines and all-day DATE labels have different representations.
Read the verified correction before skipping a gap
RFC 5545’s original section 3.3.10 contains a contradiction. One paragraph says invalid dates and nonexistent local times must be ignored and not counted. A later paragraph says a nonexistent or repeated recurrence start is interpreted like an explicit DATE-TIME under section 3.3.5. Reading only the earlier paragraph can therefore produce the wrong gap policy. [2]
Technical erratum 4271 is currently marked Verified. Reported February 12 2015 and verified February 17 2015, it corrects the earlier paragraph: invalid dates remain ignored, while generated nonexistent local times are handled under section 3.3.5. That correction resolves the contradiction for the worked examples here. [4]
For a nonexistent explicit local DATE-TIME, section 3.3.5 uses the UTC offset before the gap. For a repeated local reading, it selects the first occurrence. Applying the verified correction extends the same interpretation to generated recurrence starts. A missing clock time is consequently different from an invalid calendar date such as February 30.
The erratum’s notes also describe historical calendar-client behavior. That statement is not an observation of your current application, and no client import was performed for this guide. Keep the corrected standard interpretation and the actual destination result as separate records. The monthly date-selection guide treats a different problem: months that do not contain the requested day.
Follow all three starts through the forward gap
In the March specimen, the first start is March 7 at 02:30 with offset +0000, so its instant is 02:30Z. The next nominal weekly start is March 14 at 02:30. That reading lies inside the gap, but the corrected rule does not discard it. Use the pre-gap offset +0000 to obtain 02:30Z. [1] [4]
The fictional transition began at 02:00Z. At the selected 02:30Z instant the new +0100 offset is already active, so the corresponding local rendering is 03:30. The recurrence slot remains nominal 02:30; a rendered 03:30 is not an instruction to move every later weekly start to 03:30.
| Instance or check | Nominal local start | Interpreted instant and rendering | Decision |
|---|---|---|---|
| 1: March 7 | 2027-03-07 02:30 | 02:30Z; local 02:30 at +0000. | Ordinary first instance. |
| 2: March 14 | 2027-03-14 02:30 | 02:30Z; local 03:30 after +0100 begins. | Use pre-gap +0000; count this instance. |
| 3: March 21 | 2027-03-21 02:30 | 01:30Z; local 02:30 at +0100. | Ordinary third and final instance. |
| March 28 candidate | 2027-03-28 02:30 | Would be 01:30Z at +0100. | Not generated: COUNT=3 is already reached. |
| Explicit gap start | DTSTART;TZID=Example/Clock-2027:20270314T023000 | 02:30Z; local 03:30 after the transition. | The same pre-gap-offset interpretation applies. |
On a phone, scroll inside the table. Keyboard readers can focus its region and use the arrow keys.
March 21 has an ordinary 02:30 reading at +0100, giving 01:30Z. These are the first three instances: March 7, 14 and 21. March 28 is not a replacement third occurrence. DTSTART is the first occurrence, and COUNT limits the number of instances under the stated rule. Do not add an EXDATE or change the recurrence’s count merely to reproduce the uncorrected gap-skipping sentence. [2]
A separately specified DTSTART;TZID=Example/Clock-2027:20270314T023000 also uses the pre-gap offset. It therefore represents the same 02:30Z instant and renders 03:30 in this zone. These two readings agree because the verified correction refers recurrence starts back to the explicit DATE-TIME rule.
Choose the first occurrence of a repeated clock reading
The autumn specimen starts October 31 at 02:30 while +0100 is active, corresponding to 01:30Z. On November 7 the clock moves backward from 03:00 at +0100 to 02:00 at +0000. The local 02:30 reading then has two possible instants, an hour apart. [1]
| Instance or alternative | Nominal local start | Possible or selected instant | Decision |
|---|---|---|---|
| 1: October 31 | 2027-10-31 02:30 | 01:30Z at +0100. | Ordinary first instance. |
| 2: November 7, first | 2027-11-07 02:30 | 01:30Z at the earlier +0100 offset. | Select the first occurrence of the repeated clock reading. |
| November 7, later alternative | 2027-11-07 02:30 | 02:30Z at the later +0000 offset. | Not the selected instant; no second weekly instance is added. |
| 3: November 14 | 2027-11-14 02:30 | 02:30Z at +0000. | Ordinary third and final instance. |
| November 21 candidate | 2027-11-21 02:30 | Would be 02:30Z at +0000. | Not generated: COUNT=3 is already reached. |
On a phone, scroll inside the table. Keyboard readers can focus its region and use the arrow keys.
The earlier 02:30 uses +0100 and is 01:30Z. The later 02:30 uses +0000 and is 02:30Z. The DATE-TIME rule selects the first occurrence, so the second weekly instance is 01:30Z. A repeated local label does not by itself create a fourth recurrence instance or two meetings that Sunday.
On November 14 only the +0000 interpretation applies, producing 02:30Z for the third instance. If an organizer actually intends the later repeated instant, confirm that policy and express it through an appropriate explicit instant or supported occurrence change. Do not assume that an unqualified local 02:30 selects the later branch. Keep identity and exceptions with the export; this guide does not claim that an app’s “change this event” command writes a particular file.
Inspect two complete finite practice files
Each download has a VCALENDAR wrapper, a matching VTIMEZONE, required VEVENT UID and UTC DTSTAMP metadata, a TZID start, weekly COUNT=3 and a 30-minute duration. There are no attendees, organizers, invitations or alarms. DTSTAMP is specimen metadata dated November 18 2026; it is not the 2027 scheduled start.
The zone first supplies a +0000 standard observance at January 1 2027, then the stated forward and backward transitions. Those explicit onsets cover the six listed recurrence starts. RFC 5545 requires matching zone information valid for every recurring instance. These files are not definitions for an indefinite future series. [3]
Weekly gap practice
Download weekly gap practice (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Clock Review 1.0//EN
BEGIN:VTIMEZONE
TZID:Example/Clock-2027
BEGIN:STANDARD
DTSTART:20270101T000000
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:Practice Standard
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20270314T020000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:Practice Advanced
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20271107T030000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:Practice Standard
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:clock-gap-2027@daymooncalendar.com
DTSTAMP:20261118T000000Z
DTSTART;TZID=Example/Clock-2027:20270307T023000
RRULE:FREQ=WEEKLY;COUNT=3
DURATION:PT30M
SUMMARY:Fictional weekly gap review
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR
Weekly repeated-time practice
Download weekly repeated-time practice (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Clock Review 1.0//EN
BEGIN:VTIMEZONE
TZID:Example/Clock-2027
BEGIN:STANDARD
DTSTART:20270101T000000
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:Practice Standard
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20270314T020000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:Practice Advanced
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20271107T030000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:Practice Standard
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:clock-repeat-2027@daymooncalendar.com
DTSTAMP:20261118T000000Z
DTSTART;TZID=Example/Clock-2027:20271031T023000
RRULE:FREQ=WEEKLY;COUNT=3
DURATION:PT30M
SUMMARY:Fictional weekly repeated-time review
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR
The files contain short UTF-8 lines terminated with CRLF. Original checks parsed the complete component delimiters and three observances, converted their onsets using TZOFFSETFROM, and compared the six selected instants with independently stated offset arithmetic. They also checked both repeated-time candidates and the explicit gap start. These finite computation checks do not certify a general recurrence parser or a calendar application.
Read one complete fictional expansion review
This completed record concerns the definition and calculation of a fictional specimen. It does not claim that Rhea observed a real imported calendar or attended a meeting.
- Owner and record
- Rhea, fictional clock-review record GF-1118-A; weekly gap specimen only.
- Original recurrence fields
- TZID Example/Clock-2027; DTSTART 20270307T023000; RRULE FREQ=WEEKLY;COUNT=3; UID clock-gap-2027@daymooncalendar.com.
- Question being reviewed
- A proposed expansion omits March 14 because 02:30 is inside the forward gap, then includes March 28 as its third occurrence.
- Source decision
- Apply verified technical erratum 4271 to RFC 5545 section 3.3.10, with section 3.3.5 pre-gap-offset interpretation.
- Complete expected instances
- March 7 02:30Z; March 14 02:30Z, rendered 03:30; March 21 01:30Z, rendered 02:30. All three belong to the finite specimen.
- Completed calculation
- The independently stated UTC offsets and parsed finite timezone agree on all three instants. The gap instance is counted; March 28 is excluded by COUNT=3.
- Review decision
- Reject the skip-and-extend result for this corrected-rule specimen. Preserve the recurrence’s nominal 02:30 slots while recording the interpreted instants separately.
- Application observation and next check
- No real calendar import, display, invitation or activity was observed. Compare one isolated practice export and its supported view before editing a live series.
A second reader can identify the complete request, the corrected authority, every expected instant and the rejected result. A label such as “DST fixed” would leave the gap policy and recurrence count unresolved.
Compare the actual export with the dated expectations
Retain the source file and identify DTSTART, TZID, the matching zone, recurrence fields and any exceptions. Write the relevant nominal local reading beside its selected UTC instant. For a repeated reading, record which branch was chosen. For a gap, record the pre-gap offset and the local rendering at that resulting instant.
Read the complete original calculation results (.txt)
Original finite fictional clock calculation.
Zone Example/Clock-2027; no geographic/IANA claim.
Verified RFC 5545 erratum 4271 applied; no calendar-app import.
Gap 2027-03-14 02:00:+0000 ->03:00:+0100.
Repeat 2027-11-07 03:00:+0100 ->02:00:+0000.
File: clock-gap-weekly-practice-x36-b003.ics
UID: clock-gap-2027@daymooncalendar.com
Slot 1: nominal 2027-03-07 02:30:00; ordinary; UTC 20270307T023000Z; rendered 2027-03-07 02:30:00.
Slot 2: nominal 2027-03-14 02:30:00; gap-pre-offset; UTC 20270314T023000Z; rendered 2027-03-14 03:30:00.
Slot 3: nominal 2027-03-21 02:30:00; ordinary; UTC 20270321T013000Z; rendered 2027-03-21 02:30:00.
Fourth nominal weekly slot 2027-03-28 02:30:00 excluded by COUNT=3.
File: clock-repeat-weekly-practice-x36-b003.ics
UID: clock-repeat-2027@daymooncalendar.com
Slot 1: nominal 2027-10-31 02:30:00; ordinary; UTC 20271031T013000Z; rendered 2027-10-31 02:30:00.
Slot 2: nominal 2027-11-07 02:30:00; repeated-first; UTC 20271107T013000Z; rendered 2027-11-07 02:30:00.
Repeated-time alternative 20271107T023000Z is later and is not selected.
Slot 3: nominal 2027-11-14 02:30:00; ordinary; UTC 20271114T023000Z; rendered 2027-11-14 02:30:00.
Fourth nominal weekly slot 2027-11-21 02:30:00 excluded by COUNT=3.
Explicit DTSTART;TZID=Example/Clock-2027:20270314T023000
Same pre-gap-offset interpretation: 20270314T023000Z; rendered 03:30.
Six recurrence instants and two repeated-time candidates checked.
Complete wrappers, finite timezone, weekly COUNT=3, short UTF-8 CRLF lines checked.
Calendar application/import/display/invitation/physical activity not tested.
The output records the model’s calculations. It does not show a service import, an account’s stored record or an actual displayed appointment. If you test the files, use an isolated identifiable practice calendar supported by the service. Compare the export and view once; repeated importing can create duplicates instead of clarifying the rule.
When the destination differs, record its app/version, exact file fields, timezone information and observed instant. A shifted display may arise from zone conversion, a changed source start, a different gap policy or a changed recurrence set. The import and duplicate-review guide helps keep that investigation separate from copying or subscribing to a calendar. Before editing a real series, establish the organizer’s intended date, time, zone and branch.
Try three complete clock-transition decisions
Use the fictional zone and complete recurrence fields to explain each result before opening its answer.
Case 1
The March file starts March 7 2027 at 02:30 and repeats weekly with COUNT=3. A reviewer skips the March 14 gap and ends on March 28. Is that the verified erratum 4271 interpretation?
Show answer and explanation for case 1
No. Keep March 7, March 14 and March 21 as the three instances.
The gap start uses the pre-gap +0000 offset, giving March 14 02:30Z and a 03:30 local rendering. It is counted. March 21 is 01:30Z at +0100; March 28 is a fourth nominal slot and is excluded by COUNT=3.
Case 2
In the autumn file, November 7 02:30 can be 01:30Z with +0100 or 02:30Z with +0000. Which instant does the unqualified local recurrence start select?
Show answer and explanation for case 2
It selects 01:30Z, the first occurrence of the repeated 02:30 reading.
The earlier branch uses the offset active before the backward transition. The later 02:30Z alternative is a different instant; a repeated clock reading does not automatically create a second weekly event.
Case 3
The two practice files include three explicit 2027 timezone observances. Can this zone definition be reused unchanged for an unlimited real-city series in 2028 and later?
Show answer and explanation for case 3
No. The files establish a finite fictional 2027 example, not future geographic rules.
A referenced VTIMEZONE must supply valid zone information for every recurrence instance. Obtain the appropriate actual zone definition and intended series range before reuse. The fictional identifier and fixed 2027 onsets do not establish a city’s future transitions.
Sources and further reading
- RFC 5545 section 3.3.5 — DATE-TIME interpretationDefines explicit local DATE-TIME interpretation: use the pre-gap UTC offset for a nonexistent time and the first occurrence for a repeated time. September 2009 RFC; the guide applies these rules only to its fully stated fictional zone.
- RFC 5545 section 3.3.10 — recurrence rule and COUNTDefines recurrence expansion and COUNT. Read with verified erratum 4271: invalid dates remain ignored, while generated nonexistent local times follow section 3.3.5. The worked files use only finite weekly COUNT=3 rules.
- RFC 5545 section 3.6.5 — complete timezone definitionRequires a matching timezone definition valid for all covered instances. Defines the required observance fields and how DTSTART with TZOFFSETFROM gives an onset instant. The guide’s zone and 2027 transitions are fictional. Supporting RFC clauses 3.4, 3.6.1 and 3.8.7.2 establish the complete object/event wrapper, required event fields and UTC DTSTAMP metadata.
- Verified technical erratum 4271 — correct the gap-skipping paragraphOfficial Verified technical correction to the gap-skipping paragraph, reported February 12 2015 and verified February 17 2015 by Barry Leiba. It refers generated nonexistent local times to section 3.3.5; historical client claims are not treated as current app tests.