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,