Steps to reproduce:

I have an item configured in this way:

net.tcp.port[,8009]

Preprocessing: Discard unchanged with heartbeat (1h)

And a trigger configured in this way:

last(/Template/net.tcp.port[,\{$TOMCAT.AJP.PORT}])=0

If I restart the application the port goes down for 1-2 minutes, so the collected values are:

Result:
The trigger fires and stays in PROBLEM state for over an hour

In the above table the trigger fired at 2023-02-08 06:00:49 and resolved at 2023-02-08 07:04:48

**

While the trigger was in PROBLEM state lastest value and operational data was 1 (UP)

Expected:
The trigger should fire and stay in PROBLEM state for 4 minutes, according to the above data

NB. This happens systematically for a lot of triggers configured in this way, is not a one off problem