AJO - Jump activity sending emails twice | Community
Skip to main content
Silvio6
Level 5
August 7, 2024
Solved

AJO - Jump activity sending emails twice

  • August 7, 2024
  • 1 reply
  • 885 views

Hi, I've created two journeys using Jump activity

 

J1

 

J2

 

The custom action is sending journey data to a slack chat

 

The thing is I'm receiving that AJO data twice in slack (and I also tested using email and I'm receiving two emails)

 

Why that?

 

Thanks.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by DavidKangni

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

 

1 reply

DavidKangni
Community Advisor
DavidKangniCommunity AdvisorAccepted solution
Community Advisor
August 7, 2024

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

 

David Kangni
Silvio6
Silvio6Author
Level 5
August 19, 2024

thanks, yes, the thing was as you said, both journeys started with same Event activity. So, J2 must start with another event which is triggered from J1 (in J1 you pass the trigger attribute for J2). Regards.