HTTP error in a custom action created in adobe io to export profiles. | Community
Skip to main content
J
JoaoTo
April 14, 2025
Solved

HTTP error in a custom action created in adobe io to export profiles.

  • April 14, 2025
  • 3 replies
  • 880 views

I've created an action in adobe io that exports profiles in an adobe ajo journey, but even though it's not returning errors in my adobe io, ajo is taking a very large fraction of profiles from my action with the http error.

This adobe io code receives the data and sends it to S3 (it's arriving correctly)

example: out of 2000 profiles 1.3k are giving http errors (not timeouts) and the rest work correctly.

 

 

My app doesn't require authentication and is true for web, this is the payload I'm sending from adobe ajo to my export action:

{
"journeyId": {
"toBeMapped": true,
"dataType": "string",
"label": "nome jornada"
},
"fileName": {
"toBeMapped": true,
"dataType": "string",
"label": "Nome do arquivo"
},
"CHAVE": {
"toBeMapped": true,
"dataType": "string",
"label": "Chave"
},
"MARCA": {
"toBeMapped": true,
"dataType": "string",
"label": "Marca"
}
}

Best answer by Mohan_Dugganab

Can you check the http status code by querying the following attributes from journey_step_events dataset for the respective journey ?

 

_experience.journeyOrchestration.stepEvents.actionExecutionError AS ACTION_ERROR, _experience.journeyOrchestration.stepEvents.actionExecutionErrorCode AS ACTION_ERROR_CODE, _experience.journeyOrchestration.stepEvents.actionExecutionOriginError AS ACTION_ORIGIN_ERROR, _experience.journeyOrchestration.stepEvents.actionExecutionOriginCode AS ACTION_ORIGIN_ERROR_CODE, _experience.journeyOrchestration.stepEvents.fetchTypeInError AS FETCH_TYPE, _experience.journeyOrchestration.stepEvents.fetchError AS FETCH_ERROR, _experience.journeyOrchestration.stepEvents.fetchErrorCode AS FETCH_ERROR_CODE, _experience.journeyOrchestration.stepEvents.fetchOriginError AS FETCH_ORIGIN_ERROR, _experience.journeyOrchestration.stepEvents.fetchOriginErrorCode AS FETCH_ORIGIN_ERROR_CODE

 

3 replies

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
April 14, 2025

@joaoto Usually, the mapping attributes missing the data might throw an HTTP error. Do you see any difference between the records that got exported successfully and those that got error out?   

Thanks, Sathees
Mohan_Dugganab
Adobe Employee
Mohan_DugganabAdobe EmployeeAccepted solution
Adobe Employee
April 16, 2025

Can you check the http status code by querying the following attributes from journey_step_events dataset for the respective journey ?

 

_experience.journeyOrchestration.stepEvents.actionExecutionError AS ACTION_ERROR, _experience.journeyOrchestration.stepEvents.actionExecutionErrorCode AS ACTION_ERROR_CODE, _experience.journeyOrchestration.stepEvents.actionExecutionOriginError AS ACTION_ORIGIN_ERROR, _experience.journeyOrchestration.stepEvents.actionExecutionOriginCode AS ACTION_ORIGIN_ERROR_CODE, _experience.journeyOrchestration.stepEvents.fetchTypeInError AS FETCH_TYPE, _experience.journeyOrchestration.stepEvents.fetchError AS FETCH_ERROR, _experience.journeyOrchestration.stepEvents.fetchErrorCode AS FETCH_ERROR_CODE, _experience.journeyOrchestration.stepEvents.fetchOriginError AS FETCH_ORIGIN_ERROR, _experience.journeyOrchestration.stepEvents.fetchOriginErrorCode AS FETCH_ORIGIN_ERROR_CODE

 

G
GabrielaNa1
Level 3
July 7, 2025

Hi, I do have http error when running journeys. I tried extracting the fields above from  journey_step_events  but they are not populated. What I see though is this:

"serviceEvents": {
"stateMachine": {
"eventCode": "discard",
"eventID": "scheduledNotificationReceived",
"eventCategory": "unitary",
"eventClass": "external",
"eventType": "notSuitableInitialEvent"
}
}
 
Anybody can shed any light on what this means?
Thanks.
Mayank_Gandhi
Adobe Employee
Mayank_GandhiAdobe Employee
Adobe Employee
July 8, 2025

@gabrielana1 The system has chosen to discard (ignore) this event for this journey instance. "notSuitableInitialEvent" implies the event received is not suitable to be used as the initial triggering event for this journey/node, so AJO's orchestration logic is discarding it.

 

Some of the reasons may include: 

  • The journey or its starting node expected a different initial trigger;
  • A scheduled notification arrived in a context where it cannot trigger/start the journey profile;
  • There’s a logic or configuration preventing this notification as a journey initiator.
    Sukrity_Wadhwa
    Community Manager
    Sukrity_WadhwaCommunity Manager
    Community Manager
    April 23, 2025

    Hi @joaoto,

    Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Correct Reply.'

    Thank you!

    Sukrity Wadhwa
    Terms & ConditionsAccessibility statement

    Loading footer...