Hi SeoulForest and everyone, I’m joining this thread to share additional information regarding the reported issues with AlarmKit. While I don’t have a solution yet, I have both received user reports and personally experienced the same or similar behavior. The occurrence is rare (about once a month), but it happens consistently enough to be a reliability concern for an alarm-based feature. My Implementation Context: I have implemented a system that schedules approximately 60 fixed-schedule alarms. The Issue: Alarms occasionally fail to trigger at the scheduled time. Comparison: I set Local Notifications using the exact same date objects. These notifications arrive perfectly on time, which confirms there are no errors in the date/time logic itself. Observed Behaviors: Delayed Triggers: Alarms sometimes fire several minutes late, or in some cases, not at all for a long period. Midnight Firing: I have observed instances where an alarm that failed to trigger at its scheduled time would suddenly fire around midnight (0:00). App Launch Trigger: When an alarm has failed to trigger at its scheduled time, opening Apple’s native Clock app often causes it to suddenly fire (the Live Activity appears immediately). Environment: This behavior has been consistent from iOS 26.1 through iOS 26.4. Since the alarms do eventually fire (even if late), the alarm scheduling process itself seems to complete without any errors. I’m not certain about the internal mechanics, but it feels as though the system might not be consistently monitoring third-party alarm schedules. I would greatly appreciate any guidance or insights from anyone who has successfully resolved similar issues.