This is expected behavior. When you fire an Event (using a Fire Event Activity in an Automation or defining a schedule for the Event), a 'High Water Mark' is added to last record in the Data Extension. So, the next time the Event is fired, only new records that have been added to the Data Extension will enter the Event. Refer to this help document (specifically the 'Contacts fell below the High Water Mark' section) for further information.
However, this might be OK for your intended use. When you fire an Event, the Contacts in your Event Source Data Extension will be evaluated by the Event and providing they meet the Contact Filter Criteria (defined in your Event), then they will enter the Event.
I'm assuming that you published the new Interaction after firing the Event, in which case the High Water Mark was set on the Data Extension and the Contacts will not enter it. However, if both Interactions were published, then the Contact would enter both Interactions when the event is fired.
However, if you want all Contacts to be re-evaluated each time the Event is fired, then you will need to create a Query Activity (and include it in an Automation) to target the Event Source Data Extension and overwrite the existing records, which essentially resets the Water Mark.
Regarding the 'view event results' behavior, I'm also seeing this in the current release. You're correct in that it should indicate the percentage of rejected Contacts (that did not meet the entry criteria) and the percentage of Contacts that would have been accepted into the Interaction, but it appears that this not working at the moment.
'The Use Email Address from Entry Source Only' option determines that Journey Builder will primarily use the address provided by the entry source.
If your email addresses are not in the entry source DE, then I'd suggest you define the Channel Address Order by:
- Link to your Sendable DE containing the email addresses within an Attribute Group in Contact Builder (the DE will need to be sendable). You will need to create a 1:1 relationship back to the Contact record.
- Open Contacts Configuration in Contact Builder.
- Click 'Add Address' and select the email address field in the DE you linked to in Step 1.
- Change the Channel Address Order as required.
- Configure the journey to use the Channel Address Order in Journey Settings.
Best Answer
No. All Subscribers acts as the master list of all subscriber data, and a subscriber must be on the All Subscribers list in order for that sub to receive email. If a particular SubscriberKey has more than one email address field in a DE, the All Subscribers EmailAddress value will be updated with whatever email address is selected for the particular send.
This is quite simple - just send to the same subscriber again, but make sure to designate the primary email address as the email address you're sending to. Yes, this will update the All Subs email address again with the primary email address, but it will accomplish what you're trying to do: send to alternate email once, and then continue sending to the primary email.
A way around this could be to create a new subscriber for the alternate email address. For example, you could have SubscriberKey_PrimaryEmail and SubscriberKey_AlternateEmail. This unfortunately introduces a potential data management issue, having to account for 2 subscribers for 1 real-life identity. But from a system perspective, it could allow you to bypass the All Subs update.