We've corrected the behavior of API Extensions with multiple conditional triggers for the same resource type to ensure conditions are tied to their specific actions.

Previously, for a resource type with multiple triggers, a condition could be met and trigger the API Extension even if the action didn't match the event. For example, an Order Update could be triggered by the condition for a Create action.

After this fix, the trigger's condition is only checked when the corresponding action is performed. An Update will now only evaluate the condition for the Update action.