When monitoring SNMP sometimes a component is removed and the index no longer exists in snmp table.

For example, BGP link is down, problem created from it and then it's removed. Problem remains in Zabbix until the "Keep lost resources" period.

If this period is decreased we might remove valuable history, that might still be used, so we don't want it decrease it.

At the same time, because trigger is marked for removal at the moment, there is a high probability that the issue is no longer actual.

In this use case it would be very beneficial if we could suppress the problem automatically in case trigger is marked for removal. If it gets removed, the problem goes away anyway, but if "Marked for removal is unset", the problem continues and have correct history.