When a calendar file is updated by an external application, the change is not always noticed by the single-file KAlarm Akonadi resource which uses that file. As a result, the Akonadi database doesn't update to reflect the new file contents. It normally works correctly the first time the file is externally updated after the resource starts up, but can fail any time thereafter. Reproducible: Sometimes
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.