Is it normal that once an alarm is acknowledged it stays acknowledged even if it has been cleared in between?

A week ago a windows service was down and generated an alarm. I acknowledged the alarm and restarted the windows service again and the alarm has been cleared shortly after. Now after about one week the windows service is down again but the new alarm is still acknowledged by me. I did not know that the windows service was down again and our support team assumed that I was working on it. Is this a bug and can this be fixed or changed? Or do we have to manually unacknowledge every alarm after it has been cleared? I'm using version 12.1.

Kind regards,
Michael