Menu

Expand
Rate this page:

Warning 52303

Product: Notifications

Error - 52303

Concurrent User update

Updating the same User resource in multiple concurrent requests may cause data inconsistency. This may result in that searches using multiple Segments will not find your User resource even if it should belong to all the specified Segments.

Possible Causes

  • Updating the same User resource (e.g. adding or removing it to/from Segments) in multiple requests concurrently.

Possible Solutions

  • Change implementation so that if you need to add a User to multiple Segments at once you wait for each request to complete before trying the next one.
  • For past errors, just read the affected User resource by using the Read User API this will fix the data inconsistency.
Rate this page:

Thank you for your feedback!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Sending your feedback...
🎉 Thank you for your feedback!
Something went wrong. Please try again.

Thanks for your feedback!

Refer us and get $10 in 3 simple steps!

Step 1

Get link

Get a free personal referral link here

Step 2

Give $10

Your user signs up and upgrade using link

Step 3

Get $10

1,250 free SMSes
OR 1,000 free voice mins
OR 12,000 chats
OR more