You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 2, 2023. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: