We have identified a bug in Zabbix version 7.0.11 related to the action operation flow.

In our environment, we have configured an action with multiple operations, where steps 2 and 3 are set to execute only if the event has not been acknowledged. However, we noticed that the operations are being executed regardless of the acknowledgment status.

Our expectation is that once the event is acknowledged, the remaining operations (steps 2 and 3) should be skipped, effectively stopping the notification chain. Unfortunately, this is not happening — the actions continue to run as if the event was never acknowledged.

This behavior breaks the logic of conditional notification escalation based on acknowledgment, which is critical for our incident response process.

Please find below the configuration details and screenshots that demonstrate how the action is set up.

Steps to reproduce:

1. Create an action with multiple operation steps (e.g., step 1, step 2, step 3).

1. Set step 2 and step 3 to execute only if the event is not acknowledged.

1. Trigger an event.

1. Acknowledge the event after step 1 executes.

1. Observe that steps 2 and 3 are still executed, ignoring the acknowledgment condition.

Expected behavior: Steps 2 and 3 should not be executed if the event has been acknowledged before their scheduled execution.

Zabbix version: 7.0.11
Frontend and server on same version: Yes