Practical guide
BYHOUR and BYMINUTE: Why Two Lists Can Create Four Daily Events
BYHOUR and BYMINUTE are independent selectors. With DAILY frequency, hours 9 and 17 and minutes 0 and 30 create four daily starts, not just 9:00 and 17:30. Use separate finite series or explicit dates when the intended time slots are paired.
Identify the unintended extra time slots
A schedule designer may mean two daily reminders: one at 09:00 and one at 17:30. Encoding the hours as 9,17 and the minutes as 0,30 does not pair the first hour with the first minute. Each listed hour can combine with each listed minute.
Under this DAILY example, BYHOUR expands the day into the selected hours and BYMINUTE expands those hour candidates into the selected minutes. BYHOUR=9,17;BYMINUTE=0,30 consequently creates 09:00,09:30,17:00 and 17:30. [1]
This is a rule-construction problem even when the calendar faithfully displays all four starts. Before diagnosing duplicate imports, compare the generated times with the actual list of selectors.
Trace the four combinations and the count
On a narrow screen, swipe within this table to read the remaining columns.
| Occurrence | Date | Hour/minute combination | Start |
|---|---|---|---|
| 1 | 5 January 2027 | 9 plus 0 | 09:00Z |
| 2 | 5 January 2027 | 9 plus 30 | 09:30Z |
| 3 | 5 January 2027 | 17 plus 0 | 17:00Z |
| 4 | 5 January 2027 | 17 plus 30 | 17:30Z |
| 5 | 6 January 2027 | 9 plus 0 | 09:00Z |
| 6 | 6 January 2027 | 9 plus 30 | 09:30Z |
| 7 | 6 January 2027 | 17 plus 0 | 17:00Z |
| 8 | 6 January 2027 | 17 plus 30 | 17:30Z |
COUNT=8 counts starts. It reaches its eighth occurrence on January 6 because four starts occur per day. It does not mean eight days. The DTSTART at January 5 09:00Z matches the rule and supplies its first start. [2]
Inspect the combined-list file
These are complete fictional calendar files for inspection and isolated practice. Identifiers and timestamps belong to the examples. No invitations or alarms are present. Keep your original export and use a separate test calendar before changing a live schedule; particular calendar-app import behavior has not been tested here.
Download practice hour minute four combinations (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:74030fe737527d1d9a2e729b@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART:20270105T090000Z
DTEND:20270105T091500Z
SUMMARY:Four time combinations
RRULE:FREQ=DAILY;COUNT=8;BYHOUR=9,17;BYMINUTE=0,30
END:VEVENT
END:VCALENDARThe master interval is fifteen minutes. This UTC example deliberately avoids a missing zone component or a daylight-saving gap. It describes eight generated starts, without claiming how any particular calendar presents or imports them.
Encode two genuinely paired slots as two series
If the reader’s requirement is 09:00 and 17:30 daily, use two separate finite recurring components, each with its own start and UID. Each series carries only the intended hour and minute. Distinct UIDs identify these as two activities rather than two representations of the same recurring event. [3]
Download practice two paired time series (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:ec1ca65b7321a44b30b7c7ec@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART:20270105T090000Z
DTEND:20270105T091500Z
SUMMARY:Morning paired slot
RRULE:FREQ=DAILY;COUNT=2
END:VEVENT
BEGIN:VEVENT
UID:36e4b23fa281faeda64c4f5b@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART:20270105T173000Z
DTEND:20270105T174500Z
SUMMARY:Afternoon paired slot
RRULE:FREQ=DAILY;COUNT=2
END:VEVENT
END:VCALENDARBoth series repeat on January 5 and 6, giving four intended starts in total. Do not place two RRULE properties inside one VEVENT to obtain this union; RFC 5545 says multiple-RRULE recurrence-set results are undefined. [2]
Check selectors, count and identity separately
Write the desired complete times first, including dates and zones. Then enumerate the full combinations made by the proposed rule. Compare the result with the desired list and inspect a whole day, not merely the first and final times. A matching 09:00 and 17:30 does not prove that 09:30 and 17:00 are absent.
If using BYSETPOS to choose from a combined set, verify the resulting positions after every selector. For a simple paired-time requirement, two explicit series are easier to explain and maintain than a positional shortcut. In a live shared calendar, use its supported editor and retain an original export before replacing anything.
For location-specific local clock times, a named-zone series requires valid zone information for every recurrence. The UTC practice files here are not a promise that 09:00Z is 09:00 local time everywhere.
Two complete time-slot decisions
I see 09:30 even though I intended only 09:00 and 17:30. Is it necessarily a duplicate?
No. It is one of the four combinations in this rule.
BYHOUR supplies 9 and 17. BYMINUTE supplies 0 and 30 for each selected hour. The 09:30 start is generated directly, without another imported event being necessary.
COUNT=8 stops on January 6. Why not January 12?
There are four generated starts per day.
The first four are January 5; the next four January 6. A count measures occurrences. For two intended starts over eight days, encode and check the actual paired series and their separate counts.
Sources and further reading
- RFC 5545 §3.3.10Rule scope and exact example interpretation.
- RFC 5545 §3.8.5.3Rule scope and exact example interpretation.
- RFC 5545 §3.8.4.7Rule scope and exact example interpretation.