When a rule set has more than one action to add additional attributes, at the time of adding an event to the destination object, the rule engine considers only the mode of the first attribute value. It ignores the modes of the attributes in the rest of the actions and applies the mode that you set for the first action.
For example, if the mode specified for the first action to add the destination attribute value is after the current operation (so that attribute value is set in a modify event after the add event) and the rest of the actions to set destination attributes have the add to current operation mode, the rest of the actions also end up being part of the modify event and not the add event, as expected.
To work around this issue, move all of the actions to add destination attributes with mode after the current operation to the end of the rule set. Then the attributes with add to current operation will be part of an add event and the rest will be in a separate modify event.