I’ll try to see if I can reproduce your behaviour, but before, you may provide a bit more information, if possible.
Could you install timed-qt5-tools if not already present on your device ? (do it with devel-su pkcon refresh and devel-su pkcon install timed-qt5-tools).
With it, you can list (and delete alarms) : timedclient-qt5 -L. Can you report what is given for your looping alarm ? For instance a “normal” alarm on my device gives :
Cookie 2961 APPLICATION = 'libextendedkcal' PLUGIN = 'libCalendarReminder' TITLE = 'Rendez-vous chez le kiné' alarmtime = '2020-10-30T13:05:00+01:00' endDate = '2020-10-30T13:50:00+01:00' notebook = '3577bdc0-8cc6-47cb-bde4-b57ac436a361' startDate = '2020-10-30T13:20:00+01:00' time = '2020-10-30T13:20:00+01:00' type = 'event' uid = 'EDBCBA28-F8EB-469B-A9A4-7DA2DF44D4AE' Tick: 1604059500 (T-67872 @ 2020-10-30 13:05:00 CET) Time: 0000-00-00 00:00 MaximalTimeoutSnoozeCounter: 2 TimeoutSnoozeLenght: 1 Flags: userMode alignedSnooze reminder
While a recurring alarm has an additional action like :
Action0:
COMMAND = 'invoker --type=generic -n /usr/bin/mkcaltool --reset-alarms 3577bdc0-8cc6-47cb-bde4-b57ac436a361 EDBCBA28-F8EB-469B-A9A4-7DA2DF44D4AE'
Flags: runCommand whenServed
Which is used to reschedule the alarm to the next occurrence after this one has rung.