There is a potential bug in alerting due wrong order of definitions events on import operations.
When re-importing the same trigger, an internal set used to collect events can be unordered and potentially doesn't not update definitions correctly.
This fix for this is in image
Did some test per your suggestion, it works so change the status to verified.
Let me know if anything more to do.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.