AJO Customer Experts on Tips for Tackling Complex Journeys & Catching Error Before They Enter in Campaign

Hi @puneetla 

We don't have visibility on the roadmap. We can it to the product team. As a work around, I will say to use the datasets lookup personalization as fragments have guardrails and limitations

Thanks,

David

@puneetlamba_ 

Adobe is improving and updating the Sandbox Tooling frequently. Please check the lists of Adobe Journey Optimizer objects that are currently supported for sandbox tooling and limitations

In the August 2025 release, a main improvement is below

Sandbox tooling will now always reuse existing objects if objects with the same name are detected, to avoid object proliferation. This change applies to the following objects:

• Schema
• Field group
• Audience
• decisioning_ranking
• decisioning_rules

Support and/or Product team are working on this issue. Please open a ticket with Support to get a fix or a viable workaround.

Agree. We've abandoned incremental read because it essentially prevents journey versioning (causes incremental read to reset)

Thanks, @sukrity_wadhwa. I'm happy to be here and looking forward to hearing from the community!

Hi @puneetlamba_, refreshing the page will update the thread with any new responses. You’ll also receive a notification via the bell icon on your community profile whenever there’s a new comment or reply. 

I'm not aware of this specific issue but I'd start by focusing troubleshooting on your Mobile SDK implementation. 

Use Assurance to validate that the events you've configured as triggers within Journey Optimizer are, in fact, being fired when expected. It may be that there's a reason within your implementation that the events that trigger the message are not being fired.

In the event that you've validated that, I would also double-check the frequency settings within the in-app message configuration.

If you've already validated that the events are being fired as expected and the frequency settings are not going to block the expected message display, then I'd open a ticket. In the event there's actually a bug, leveraging the details from the debugging done in Assurance (mentioned above) will help narrow in on the specific issue with engineering.

There's no out-of-the-box alerting option for this specific scenario but there's a few ways to approach this.

• If your marketing teams are already using planning tools (such as Workfront) that allow for custom notifications or reminders to be configured, you can build these reminders into your planning templates there.
• A simpler, alternative, option would be to incorporate the inclusion of "Journey check-in" reminders in your journey/campaign set-up process. Whenever a team member is developing and publishing a journey, they would create a reminder in their calendar to check-in either at a set point within the journey duration or a few days before it's intended to expire. This would ensure any journeys which may require action will not be missed.
• A complementary option would be to develop a tagging structure within Journey Optimizer that identifies journeys or campaigns expiring on a set day, week, or month. Your team could then build an activity into their day-to-day activities where they filter on those tags and review any campaigns which will be expiring soon.

Adobe Experience Platform provides several predefined alert rules that you can enable.

Here is a tutorial to subscribe to data ingestion alert using Adobe I/O Events notifications

You can leverage this approach with Observability Insights to build your own monitoring/alerts

As of today, AJO offers several tools for conflict management and prioritization. These tools are available for campaigns and unitary, Audience Qualification, and Read audience journeys.

• Conflict detection tool
• Priority scores
• Rule sets

Find mor details here