Hi Team,
We’re using a custom action in the journey to trigger an HTTP call to a downstream API service, which transfers journey data to a third-party system.
I’ve ensured that all journey data is unique, with no duplicates on our end.
However, upon reviewing the data in the third-party system, we’ve noticed a small number of duplicates that 18 duplicate records (entire record remain the same) out of approximately 40,000. It’s been difficult to identify the root cause or determine whether this behavior occurs from the nature of the custom action itself.
Could you please help investigate or provide any insights into what might be causing this issue?
Thanks,
Views
Replies
Total Likes
Kindly check if the count of profiles that were successfully sent to the API service are matching with what you see downstream (by querying step events dataset) to isolate the issue further.
Also, if there is a timestamp / date captured in the downstream logs, that would help in determining as to when the duplicates occurred.
There should ideally be a constraint on the downstream service not to allow the duplicate entries to be recorded.
Thank you!
I used the following query to find out the reason:
however, actionName is blank and execution_count has 7 times unable to be linked which action nodes generated 7 times.
why is that? and how come it was triggered 7 times instead 1 as the profile is unique flowing into one branch to the action node and there is no one else timeout node to retry.
SELECT
_experience.journeyOrchestration.stepEvents.profileID AS profileID,
_experience.journeyOrchestration.stepEvents.actionName,
COUNT(*) AS execution_count,
MIN(timestamp) AS first_execution,
MAX(timestamp) AS last_execution
FROM journey_step_events
WHERE
_experience.journeyOrchestration.stepEvents.profileID = '8524321'
AND DATE(timestamp) = DATE('2025-10-06')
GROUP BY _experience.journeyOrchestration.stepEvents.profileID,_experience.journeyOrchestration.stepEvents.actionName
HAVING COUNT(*) > 1
profileID,actionname,execution_count,first_execution,last_execution
8524321,,7,"10/06/2025, 12:00 PM","10/06/2025, 12:17 PM"
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies