Hi @silvio6,
As several journeys can use the same event, if you are using the same event in your 2 journeys then it's an expected behavior.
If J1 and J2 are using the same event, they both triggered when received the event. J2 probably sent the first comms and J1 jump to J2 then sent the 2nd comms.
You can use the query below to find the exact order
select _experience.journeyOrchestration.stepEvents.*
--_experience.journeyOrchestration.stepEvents.nodeID AS nodeID,
--_experience.journeyOrchestration.stepEvents.nodeName AS nodeLabel--,
--count(1) stepEnteredCount
from journey_step_events
where --1=1
_experience.journeyOrchestration.stepEvents.journeyVersionID IN ('J1 Version ID','J2 Version ID')
--AND _experience.journeyOrchestration.stepEvents.journeyNodeProcessed = TRUE
AND _experience.journeyOrchestration.stepEvents.nodeName = 'Your event name'
order by timestamp desc
Thanks,
David