Skip to main content
HarshitJo1
HarshitJo1
Level 2
May 21, 2026
Question

Code-Based Experience (CBE) Conflict: Journey Wait Activity overriding higher-priority Campaign

  • May 21, 2026
  • 3 replies
  • 37 views

Hello Community,
​I am looking for clarification on the prioritization logic in Adobe Journey Optimizer (AJO) when a Code-based Campaign and a Code-based Journey are active on the same surface.
​The Scenario:
I have a Code-based Campaign and a Code-based Journey targeting the exact same surface URL.
​Campaign Priority: Set to a higher score.
​Journey Priority: Set to a lower score.
​The Observation:
​On First Visit: The Campaign experience is displayed (as expected based on priority).
​On Second Visit: The Journey experience is displayed, even though the Campaign is higher priority.
​The "Journey State" Factor:
Within my Journey, once a user qualifies, they trigger a Code-based Experience action, which is immediately followed by a 21-day Wait activity.
​I suspect that once the user enters the Wait period, they are considered "realized" or "locked" in that journey state. My hypothesis is that because the profile is effectively held within that journey instance for the 21-day duration, the system is prioritizing the journey's existing state over the priority score of any new competing Campaigns.
​My Questions:
​Expected Behavior: Should a higher-priority Campaign always override a Journey's CBE, even if the user is currently in a "Wait" step within that Journey?
​Persistence: Does the Journey engine treat a user in a "Wait" activity as having an active "experience lock" on that surface, effectively bypassing the real-time priority evaluation?
​Recommendations: If this is intended behavior, what is the best practice to allow a higher-priority Campaign to "interrupt" or override a user who is currently in the middle of a Journey wait period?
​I have verified that the priority scores are distinct and the surface URLs are identical. Any technical insight into how the Edge decisioning engine evaluates this specific "Active Journey vs. New Campaign" conflict would be greatly appreciated.

      3 replies

      HarshitJo1
      HarshitJo1Author
      Level 2
      May 21, 2026

      "Update on my observation: I have identified a significant bottleneck where 99% of my traffic is stalling at the Code-Based Experience (CBE) action node and failing to progress to the subsequent Wait activity.
      ​My Questions:
       If so, what is the best practice for ensuring the AEP Web SDK correctly signals the completion of this action to prevent journey queues?

      A
      AsishPa1
      Level 1
      May 21, 2026

      This is an interesting scenario. I believe Campaigns are quick as these are meant for in-moment experience (where we would expect the offer returned in milli-seconds). Whereas the journey has some latency for the first visit as it has to go through the journey steps. I think that is why you saw content from Campaign CBE on the first visit. Even though the Journey CBE didn’t send its content back to the App, the profile has entered the journey and waiting. In the second visit of the same profile for same surface URI, there are competing contents from both campaign and journey. As the campaign priority is higher, i would expect Campaign experience ideally. But since you are seeing the journey experience, it seems to me then the priority is not working. Or AJO is just rendering the content based on who gives the offer first and priority will come into play if both the offers are returned at the same time. Since Campaign Journey uses diffrent paths in AJO blueprint my guess is there will be always different timelines.

       

      Also, out of my curiosity, what was your use case to send separate content (one from campaign and one from Journey) for the same surface uri ?

        HarshitJo1
        HarshitJo1Author
        Level 2
        May 22, 2026

        Journey CBE was already live in the same surface URL. We made a new CBE campaign live for A/B testing in same surface URL.I thought as we have priority higher in case of campaign this issue might not occur and Campaign experience will be shown.Do you think as profile got stuck in the journey?This could be the reason.

         

        I have also identified a significant bottleneck where 99% of my traffic is stalling at the Code-Based Experience (CBE) action node and failing to progress to the subsequent Wait activity. 

        SupratikSe
        SupratikSe
        Level 2
        May 22, 2026

        I think Adobe Journey Optimizer uses priority to resolve code-based conflicts on the same surface. The built-in Wait after a code-based inbound action is journey flow control, not a documented surface-level lock. If a lower-priority journey appears to win after the first visit, the likely cause is implementation/state handling rather than the documented priority model. For the Web SDK, the code-based experience must be fetched, rendered, and followed by a decisioning.propositionDisplay event; that display notification is the key completion signal to validate when troubleshooting journey stalls.

          HarshitJo1
          HarshitJo1Author
          Level 2
          May 22, 2026

          To add a point here that earlier I was thinking that profile is stuck in the journey wait node

          But when i check the profile for the past two days it is in custom action node. i have also  have identified a significant bottleneck where 99% of my traffic is stalling at the Code-Based Experience (CBE) action node and failing to progress to the subsequent Wait activity.

           

           

          Terms & ConditionsAccessibility statement

          Loading footer...