journeyStep events action execution fields
This mixin will be shared by the journeyStepEvent and journeyStepProfileEvent.
If the step has an action to be processed, those fields will be added to the event payload.
ID of the action that is being executed.
Name of the action. If no name has been set, the stepName will be taken.
Type of the action.
Indicates if the action is parameterized or not.
The amount of time (in milliseconds) taken to execute a current action.
Type of error that happens when the action is called.
Code for action execution error. Present if the error has a code, such as an HTTP one.
A timeout can occur, in two cases:
- at the first attempt an action is executed. In this case, the execution is not finished, so there is no underlying error
- on a retry: in this case, the actionExecOrigError/actionExecOrigErrorCode describes the error encountered on the attempt before the retry.
For instance, an email is being sent and an HTTP 500 error is returned at the first attempt. The fetch is retried, but the duration of the 2 attempts exceeds the timeout. Then the action execution is tagged as timedout. The action part will look like:
... "actionId": "myActionId", "actionName": "My mail sending", "actionType": "acsRestAction", "actionParameterized": true, "actionExecError": "timedout", "actionExecOrigError": "http", "actionExecOrigErrorCode": "500"
Error code of the actionExecOrigError.
Indicates the type of action.
- ACS Email
- ACS SMS
- ACS Push
This describes the delivery Job Id for the batch Journey.
This describes the delivery Id for the batch Journey.
This describes if the Batch Journey is triggered from Audience Segment.
Count of scheduler notification requests sent to the scheduler service during the step processing.