We are currently using .updateConversationField method in our service to transfer a customer to another agent. Our service is a REST API that transfers a customer using a single instance of the LE Node.js bot.
Is it safe, after all? I mean, we are calling .updateConversationField like this:
from our request handling logic. Which means, that we can initiate a call to.updateConversationField multiple times, without waiting for response, and then our callbacks are an async functions, that are, also, divided into multiple async phases.
Will node-agent-sdk handle this concurrent flow correctly?
What are the best practice, of using this lib in race situations?
We are currently using
.updateConversationField
method in our service to transfer a customer to another agent. Our service is a REST API that transfers a customer using a single instance of the LE Node.js bot.Is it safe, after all? I mean, we are calling
.updateConversationField
like this:from our request handling logic. Which means, that we can initiate a call to
.updateConversationField
multiple times, without waiting for response, and then our callbacks are anasync
functions, that are, also, divided into multiple async phases.Will
node-agent-sdk
handle this concurrent flow correctly? What are the best practice, of using this lib in race situations?