When the problem happens while maintenance period because of "nodata" trigger and then data has been processed by Zabbix server (possible delay from proxy or unavailable active agent) and resolves while maintenance.

Immediately after maintenance ends, Zabbxi generates new event with PROBLEM status, but do not change trigger status. In this case we have action escalation which will be never stopped because of trigger OK status.