Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate customer after simultaneous request with same id #2

Open
adexot opened this issue Jun 26, 2022 · 1 comment
Open

Duplicate customer after simultaneous request with same id #2

adexot opened this issue Jun 26, 2022 · 1 comment

Comments

@adexot
Copy link

adexot commented Jun 26, 2022

I see duplicate customer with the same id when I make a simultaneous call with addAttribute and track methods.

Screenshot 2022-06-26 at 12 02 46

One thing to note is that the identify call was not made for the customer creation on engage. The duplicate customer data should ideally be one, since the call is made to the same id.

@adexot adexot changed the title Duplicate customer after simultaneous request with Duplicate customer after simultaneous request with same id Jun 26, 2022
@kehers
Copy link
Member

kehers commented Jun 28, 2022

@adexot

Thanks for discovering this and sorry about the inconvenience. It is most likely due to race conditions with both calls triggered at the same time. A temporary fix would be to await for each call like this:

await Engage.identify({...})
...
await Engage.track('id', {...})

We will refactor to solve this internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants