There are few (or not) information triggers about an operating system update, some hardware module replacement, etc.
Years ago it was working in an easy way: something happened, trigger appeared, then disappeared because there’s no reason for him to live.
Recently we had a new field “recovery expression” created, which prompted someone to change the logic of information triggers’ disappearing. Now you need to “ack to close” them. Until then, they never disappear.
As for me, a monitoring specialist, I don’t want to ack every problem someone’s caused.
As for system administrators, they don’t want to learn how close those problems (they’re asking to make triggers automatically disappearing).
Please, return the obvious behaviour.