AJO- Discarded Profiles | Community
Skip to main content
A
AviBarge
January 16, 2025
Solved

AJO- Discarded Profiles

  • January 16, 2025
  • 2 replies
  • 2005 views

Hello Community,

I have the following questions regarding discarded profiles that are logged in the Journey Step Event dataset/schema:

  1. How can I obtain detailed information about why a profile was discarded? We have the eventType(has Reason shortform) in the schema under serviceEvent.stateMachine and serviceEvent.dispatcher, but I'm having trouble understanding the reasons.

  2. What is the difference between the serviceEvent.stateMachine and serviceEvent.dispatcher objects in the Journey Step Event dataset/schema?

  3. Once an event hits AEP and is eligible to enter the Journey but somehow gets discarded, how can I capture that information and send it back to a third-party platform to retrigger? The Journey Step Event only contains the Profile ID, so how can I identify the specific event associated with that profile?

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 Anuhya-Y

I guess that you have already verified the namespace of the profile with the unitary event as well for these profiles that didn't enter the journey. However, if you still believe the profile event is carrying the correct information but is not qualifying for the event and not entering the journey, please reach out to the Adobe support team for further assistance.

Kindly note that if profiles do not enter the journey, any audit information for those profiles will not be recorded in the journey_step_events table.

2 replies

Anuhya-Y
Community Advisor
Anuhya-YCommunity Advisor
Community Advisor
January 16, 2025

Hi Avinash,

Check out AJO schema dictionary for a detailed description of fields https://experienceleague.adobe.com/tools/ajo-schemas/schema-dictionary.html?lang=en

 

Check out actionExecutionErrorCode, actionExecutionError from journey_step_events fields to understand error  . Once http error code is known, can understand a bit more info on the error's root cause in general.

 

sample query

 

select 

_experience.journeyOrchestration.stepEvents. actionExecutionErrorCode,

               _experience.journeyOrchestration.stepEvents.actionExecutionError,

               _experience.journeyOrchestration.stepEvents.stepStatus

from journey_step_events 

where

      _experience.journeyOrchestration.stepEvents.journeyVersionID IN ('b2433e9c-6711-404e-813e-c38fba02ec83')

 

You can use custom action to share info with 3rd party system or store the failed events back into AEP data set to trigger journey again. Check out

 

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/journey-use-cases/technical-use-cases/custom-action-aep

https://experienceleaguecommunities.adobe.com/t5/journey-optimizer-questions/event-triggered-journey-what-about-there-is-a-event-failure/m-p/727965#M3474

 

 

 

                                  

 

A
AvinashVi
January 17, 2025

Hello @anuhya-y ,

 

Thanks for your thought, I will elaborate the the problem statement here,

so By below Query i am getting Discarded profiles (event ingested in Experience Schema but not entered in Journey).

 
 SELECT   *  FROM journey_step_events
where  TIMESTAMP > (now() - interval '24' hour) and
  _experience.journeyOrchestration.stepEvents.journeyVersionID IN ('<jrny_versionID>') and
(_experience.journeyOrchestration.serviceEvents.dispatcher.eventCode = 'discard' 
      or _experience.journeyOrchestration.serviceEvents.stateMachine.eventCode = 'discard' )
    order by TIMESTAMP
 
We will get discarded profile Ids from last 24 hours and need to re trigger this.
 
Thanks,
Avinash
Anuhya-Y
Community Advisor
Anuhya-YCommunity Advisor
Community Advisor
January 17, 2025

@avinashvi 

Couple of questions regarding the journey setup:

  1. Could you please confirm the type of event being used?
  2. Is this the first event in the journey?

 

A quick note: If a specific event type is not qualified by the profile or system action, the profile will not enter the journey where the event is used. Consequently, any audit information for such profiles will not be captured in the journey_step_events table.

Additionally, if the event is not the first in the journey, it might be helpful to enable the event timeout path and include a custom action to send data back to the third-party system

Terms & ConditionsAccessibility statement

Loading footer...