We face a request to update email address that is used for sending in active journey (address could be changed throughout the lifetime of the journey and we need to use up-to-date one). Additional complexity comes from the fact that we have multiple emails per contact and use SQL for the identification of emails for each journey (based on some business logic). Apparently we need to use "email attribute from Contacts" and create a unique population per journey but that does not seem as viable option.
Any other solutions you might think of?