When calling the api to update the customer attribute, the order is reversed. My first request was updated later than the later request, resulting in an attribute update error. Is there any good solution?
Solved
When calling the api to update the customer attribute, the order is reversed.
Best answer by Penny
Hi Jones!
Typically API calls are processed in order, but we do not guarantee that things will be processed in the exact order they are sent. As our application has multiple services if one happens to have a queue of things being processed it's possible that they could be processed slightly out of order.
If you're pushing attribute updates via multiple calls in quick succession, you could see a case where the first request may not have been completed before the second one was processed.
In such scenarios, if the order of the attribute update is important, we would recommend throttling the requests to provide sufficient time for the first request to be processed.
Hopefully this helps to clarify! 😊
Hi Jones!
Typically API calls are processed in order, but we do not guarantee that things will be processed in the exact order they are sent. As our application has multiple services if one happens to have a queue of things being processed it's possible that they could be processed slightly out of order.
If you're pushing attribute updates via multiple calls in quick succession, you could see a case where the first request may not have been completed before the second one was processed.
In such scenarios, if the order of the attribute update is important, we would recommend throttling the requests to provide sufficient time for the first request to be processed.
Hopefully this helps to clarify! 😊
Penny wrote:
Hi Jones!
Typically API calls are processed in order, but we do not guarantee that things will be processed in the exact order they are sent. As our application has multiple services if one happens to have a queue of things being processed it's possible that they could be processed slightly out of order.
If you're pushing attribute updates via multiple calls in quick succession, you could see a case where the first request may not have been completed before the second one was processed.
In such scenarios, if the order of the attribute update is important, we would recommend throttling the requests to provide sufficient time for the first request to be processed.
Hopefully this helps to clarify! 😊
Thank you for your suggestion, I have solved the probability of this problem by delaying the call
1 person likes this
Reply
Most helpful members this week
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.