AJO Push Notification Campaign – Most Profiles Bounced with "PushNoMessageFoundForDecisionPath" | Community
Skip to main content
S
SherinJo1
Level 2
May 1, 2026
Question

AJO Push Notification Campaign – Most Profiles Bounced with "PushNoMessageFoundForDecisionPath"

  • May 1, 2026
  • 1 reply
  • 21 views

 

Hi Community,

I am facing an issue with an Action Campaign in Adobe Journey Optimizer (AJO) for sending push notifications related to custom announcements.

Scenario

  • I created an Action Campaign for push notifications.

  • Triggering rules have been configured.

  • The audience is batch evaluated.

  • The campaign activates successfully.

However, after activation:

  • Only a few users actually receive the push notification.

  • In the campaign report, I can see that Targeted and Sent counts are almost the same.

  • But a large number of profiles are showing as Bounced.

  • One of the error reasons I see is: PushNoMessageFoundForDecisionPath

Note:

  • This is currently being tested in a Dev environment. The mobile app currently has only around 20–30 active users. Users may or may not have granted push notification permissions. Push notifications from Journeys using the same audience seem to work.

Questions

  1. What exactly does the error PushNoMessageFoundForDecisionPath mean in the context of AJO push campaigns?

  2. Under what conditions does AJO mark a push notification as bounced with this error?

  3. Could this be related to:

    • Missing push tokens/Invalid device registrations?

  4. Is there any troubleshooting approach recommended to identify why only a subset of users are receiving notifications?

  5. Are there specific datasets/logs/events in AEP or AJO that should be checked for deeper debugging?

Any guidance or troubleshooting suggestions would be greatly appreciated.

Thanks!

1 reply

Mayank_Gandhi
Adobe Employee
Mayank_GandhiAdobe Employee
Adobe Employee
May 4, 2026

​@SherinJo1 PushNoMessageFoundForDecisionPath is much more likely a message-resolution / decisioning-content problem than a push token / device registration problem. In practice, it usually means AJO evaluated the profile down a path that should have produced push content, but no renderable message payload was found for that evaluated path at send time. If your campaign uses decision policies / offers / dynamic content selection, that is the first place I would investigate. If it does not use decisioning, then this error is unusual enough that I'd treat it as a likely configuration defect or a product issue and collect evidence for support.

Terms & ConditionsAccessibility statement

Loading footer...