What's the difference between a recurring alarm and a recurring event?
A recurring alarm is a system-level alert scheduled to fire at a fixed time on a repeating basis, built to break through Silent mode and Focus. A recurring calendar event is a data record with a recurrence rule attached to it, and by default that record only produces a notification, not an alarm.
The distinction sits in how iOS treats each one. EKRecurrenceRule is a class that describes the pattern for a recurring event, and that pattern lives inside EventKit as metadata: a frequency, an interval, maybe an end date. It tells Calendar when the event repeats. It says nothing about how loudly, or whether, you get warned. A Clock app alarm works the opposite way — it doesn't know about a calendar at all, it just knows a time to ring, every day you told it to. Confusing the two is the root of most "why didn't my meeting alarm go off" complaints, which we cover in more detail in I keep missing meetings, what fixes it.
Why does a repeating calendar event alarm silently stop firing?
Because the default calendar alert is a notification, and notifications are exactly what Silent mode and Focus are designed to suppress. A recurrence rule guarantees the event shows up on your calendar every week; it does not guarantee the alert survives the phone's own volume and interruption settings.
This is the gap AlarmKit closes. An alarm is a prominent alert for things that occur at a fixed, pre-determined time, based on a schedule or a countdown, and when it fires, the alert breaks through the silent mode and the current focus. A standard calendar notification has no such guarantee. Apple's own AlarmKit session frames the problem plainly: apps built on regular notifications stay quiet unless the app holds a rarely granted entitlement, while AlarmKit alerts cut through silent mode and focus with a permanent banner and sound. That's the whole reason repeating 9am standups and weekly one-on-ones get missed even though the event has been sitting on the calendar, correctly recurring, for months. We go deeper on the mechanism in what is AlarmKit and why it matters.
How do you set an alarm for a repeating meeting that actually rings?
Attach the recurring event to an app that converts EventKit or calendar-API data into a real AlarmKit alarm, rather than relying on the calendar's built-in alert. The recurrence rule stays on the event as it always has; what changes is the delivery mechanism for each occurrence.
Pealo does this by reading the event's recurrence pattern from Google Calendar, Outlook, or iCloud and scheduling a matching AlarmKit alarm for every occurrence, so a weekly meeting alarm setup takes one pass instead of a manual repeat each Monday. The steps are the same regardless of which calendar the meeting lives on: connect the account once, pick a lead time, and every future occurrence of the recurring event inherits it. For calendar-specific setup, see loud alarms for Google Calendar events, Outlook calendar alarms that actually ring, or alarms for iCloud calendars on iPhone depending on where the recurring meeting is booked.
Should you rebuild the meeting as a Clock app alarm instead?
No, because a Clock app alarm has no connection to the calendar record, so any reschedule, cancellation, or one-off exception in the meeting series has to be copied over by hand. A recurring event that changes time on one Tuesday because of a holiday will silently drift out of sync with a manually built Clock alarm.
The trade-off is real and worth mapping out before choosing a workflow.
| Behavior | Manual Clock alarm | Calendar-linked alarm |
|---|---|---|
| Follows meeting reschedules | No | Yes |
| Skips cancelled occurrences | No | Yes |
| Rings through Silent/Focus | Yes | Yes |
| Setup per new recurring event | Manual, every time | Automatic |
| Handles multiple calendars | One at a time | Yes, combined list |
The full breakdown of this trade-off, including where Clock still wins, is in Clock app vs calendar alarm app. If you're juggling a work calendar and a personal one, work and personal calendars, one alarm list covers merging both into a single alarm feed rather than maintaining two sets of repeating alarms.
What happens when a recurring event changes time or gets skipped?
A properly linked calendar alarm updates or cancels automatically because it reads the live event data rather than a fixed schedule set once and forgotten. This matters most around holidays, daylight saving shifts, and the occasional meeting that gets bumped an hour.
Under the hood, the interval of an EKRecurrenceRule specifies how often the recurrence rule repeats over the unit of time described by its frequency — but individual occurrences can still carry exceptions that override the pattern for one date only. An alarm scheduled from a snapshot of the rule won't see that override; an alarm scheduled from the live event will. This is also why time-zone edge cases trip people up on recurring meetings that span regions, a problem detailed in calendar reminder wrong time zone, causes and fixes.
Who's behind fixing this on iOS?
Pealo is built specifically to turn recurring calendar events into recurring AlarmKit alarms, without needing a separate sign-in for iCloud calendars or a rebuilt schedule every time a meeting series changes. The background and reasoning for the app are laid out on the About Pealo page, and a side-by-side against other calendar alarm tools is in best calendar alarm apps in 2026, 9 compared.
Alarms your calendar sets for you
Connect Google, Outlook or iCloud. Pealo arms a real alarm before every event.
Download on the App Store