Some users fail to call people.set, but the callback succeeds

[cvvix]

I found that some users fail to call people.set, but the callback succeeds
Initially, I noticed a batch of registered users without the profile information specified by my project in the mixpanel panel, suspecting it was because these users left too quickly and didn't have time to report
Later, I added a successful set point in the set callback, and found that this point could be successfully reported and displayed, with the data also being normal
Therefore, it's possible that for some reason, the merge of set reporting cannot take effect

example

login

mixpanel.identify(userId)
mixpanel.people.set({...}, () => {
mixpanel.track('MixpanelSet', {userid}, {send_immediately: true})
})

Version: 1.71.0
User Behavior: Both those who exit quickly and those who stay on the page longer have completed MixpanelSet reporting
User Devices: Apple 15.7+

[tdumitrescu]

Unfortunately the SDK doesn't have visibility into the success of processing operations, just into whether data makes it to the API edge. Once event or profile data has reached the server, it gets processed asynchronously. And in the SDK's default batching mode, the event/profile tracking methods return a boolean saying just whether the data was enqueued successfully for delivery over the network. There are then asynchronous systems in the SDK that will try to flush that data out over the network, retry if it fails with temporary network errors, etc.

[cvvix]

Since mid-October, about one-third of users have failed to merge identity data with people.set every day. Is this normal?

[tdumitrescu]

No, it's not. This is something you should discuss with customer support, who can look at specifics of your implementation. They'll get you smarter and quicker help than GitHub SDK maintainers!