Hi, agree with the other comments you may need to run some code and build a data set.
Find the reasons you wopuld like to include in the failure list:
select distinct _experience.customerjourneymanagement.messagedeliveryfeedback.messagefailure.reason
from ajo_message_feedback_event_dataset
and then run some data distiller writing to a profile enabled enrichment table that you can query, something like:
insert into <table>
select struct <your layout, probably profile primary id and timestamp >
FROM
(
select identitymap['your primary namespace'][0].ID
from ajo_message_feedback_event_dataset
where _experience.customerjourneymanagement.messagedeliveryfeedback.messagefailure.reason in ('your','chosen','reasons')
)
something along those lines should work
Another one to try test, and I'm not sure how it will see it exactly, but on the email in the journey, click the 'other path for timeout and or error' and see if those profiles go down that leg. If so, add an update task and update the pfile with a field that marks the email as invalid and needs the second message. Not sure on that one, but also worth a try
cheers
Marc