@Mario248 This behavior is by design.  AJO modifies HTML formatting to enforce structural and security requirements. When you save HTML, AJO's backend parses and sometimes "minifies" or restructures your code for consistency, validation, and security reasons. It will not retain line breaks, indentat...

@NestorAr A notification working in Assurance but failing in a journey typically points to an issue in push channel configuration, token/surface selection, or related credentials Check if the App ID used in the profile/token collected from the device matches the App ID specified in the Channel Surfa...

@Saiteja_1225 https://certification.adobe.com/courses/199 always use the Adobe certification portal to schedule and book any adobe exam.https://certification.adobe.com/certification/journey-optimizer-developer-expert?%2Fcertification%2Fjourney-optimizer-developer-expert=&tab=certificate5

@riyaA  Can you Reference contextual fields directly? {{context.journey.events.923737463.LEAD_88_8_05.discountedPrice}}  

@SherinJo1 lets start with permission check:   Go to Permissions UI in AEP.Attach yourself to a role that grants "Manage message presets," or ask a system admin to do this if you can't access permissions directly.Must be part of AEP-Default-All-Users and any relevant product profiles in the Admin Co...

@mrgupta were you able to raise the ticket for this?

@Pradeep-Jaiswal Try  Test Mode (before publishing the journey), you can: Run the journey with test profiles.See detailed logs in the UI (request body, endpoint, status code, sometimes response content).Validate the structure and value of requests and responses in JSON format visually. https://exper...

@AlexandreSa8 When you create a relationship between two schemas of different classes (e.g., XDM Individual Profile for Customer and a Custom Class for Booking), the attributes of the destination schema (Booking) are not automatically surfaced as attributes of the Customer profile in the Profile UI ...

@LuisCardenas  Emulate at Scale (Recommended for Accuracy) Use a test segment of >1000 profiles in a dev/sandbox environment.Trigger your custom unitary event for the segment.Observe distribution - results should match your split/cap logic.

@LuisCardenas You are mostly correct. Profile caps and percentage splits are designed for journeys involving at least 1,000 profiles to ensure reliable results. If you set a cap to 1, you’ll see inconsistent behavior because the system wasn’t designed to enforce hard “single-slot” consumption. https...