Bot users may be disabled due to multiple failed login attempts because of the account login policy which prevents users from logging in from unauthorized (non-whitelisted) IPs, or the connector may be offline due to an error.
- If the bot users are disabled due to multiple failed login attempts.
Due to the account login policy which prevented users from logging in from unauthorized (non-whitelisted) IPs. Please reach out to your LivePerson account team to add IP addresses used by the servers where bot services are running
- If the connector is offline click on the details to view the error
- Failed connection: In the event of a failed connection, wait some time, and then try to stop and restart the connector. If you still need assistance, please contact your LivePerson representative.
- 401 "unauthorized" error: This error can occur if you try to add an agent connector for a bot user that wasn't created by you. Either add the agent connector for a different bot user created by you, or have the creator of the bot user add the agent connector.
When a consumer initiates a conversation, the conversation is assigned to the bot skill and assigned to the bot user. But on the back end the bot user doesn’t pick up the conversation and thus doesn’t respond to the conversation. The conversation stays in limbo in the Conversational Cloud without responding.
When the consumer initiates the conversation we get the ExConversationChangeNotification but we do not get the messagingEventNotification that should follow. We use the messagingEventNotification to respond to the conversation.
There is a method called agent.subscribeMessagingEvents that you should use to subscribe to the events of each individual conversation.
In the current version of the Messaging API, even if you don’t use subscribeMessagingEvents explicitly, you will be notified of messaging events. But sometimes notifications are not sent (usually the first notification in the conversation).
Explicitly subscribe to the messaging events for each conversation that you want to follow. This will fix the bug and at the same time ensure compatibility with future versions of the API (that will not automatically subscribe to conversations).
This approach is demonstrated in this bot example.
After a server restarts, the bot did not respond to ongoing chats that had begun before the restart. This should not be happening because chat bots are not logged out when there’s a server restart – our back-end servers keep the bot sessions “alive”.
After the restart the Bot didn’t continue to try to respond. This caused the visitor to give up and abandon the chat.
Developers should add a retry mechanism to their Bot. The mechanism should take restarts into account. For details, see Retry Policy and KeepAlive Best Practices in the LivePerson Developer Center.
- Two out of four of our bot agent users are being disabled by the system shortly after logging in.
- All four bots have the same setup.
- When our agent manager enables the two bot agents, they are disabled again after a minute or two.
Why is the system disabling these two bots and not the other two which are connecting with the same code?
- The bot user exceeded the allowed login attempts.
- Each account has a login policy that determines after how many login attempts a user will be disabled. The bot user in this case had exceeded the number of login attempts allowed by his account, causing his user profile to be disabled.
- Login failure due to login policy
- The cause of the bot user login failures was due to the account login policy which prevented users from logging in from unauthorized (non-whitelisted) IP addresses.
- The server from which the bots were ‘logging in’ have a dynamic IP. Due to the account’s login policy the generated IPs were often not in the customer’s whitelist.
- Since the bots were hosted on different servers they didn’t share the same IP. This is why only two bots were impacted.
Do one of the following:
- Place a static IP on the server where the bot service is hosted and add the IP to the account’s Login Policy whitelist.
- Within the Login Policy, whitelist the full IP range used by the servers running bot services. Please contact your LivePerson account team to help you with this.
- If you are using dynamic IPs, you can place an alert on your side to notify you immediately when IPs of the host (where bots are running) change. This way you can take relevant steps, if required.
Bot agents cannot initiate conversations; they can only respond to consumer requests or resume conversations that they resolved previously.
Starting a conversation consists of two separate, unlinked, requests (both sent from the consumer side).
- A request to open a conversation.
- The first message.
In the issue described above, the request to open a conversation was sent, and, in addition, one or more of the following occurred:
- The first consumer message did not reach the Conversational Cloud system.
- The consumer may have received an automatic message before sending his first message (open conversation default).
- Due to Bot speed, the Bot sent the first message before the consumer message was fully processed and displayed (a matter of milliseconds).
The system is working properly.
The bot’s engagement window opens but it is empty and consumers see a warning icon (red triangle) next to the messages that failed.
- Network problems on consumer side. This can occur at any point in the conversation when the consumer tries to send a message. The message doesn’t not reach the Conversational Cloud system and the result is an empty conversation window on the agent side.
- The consumer, who was messaging via the SMS connector, sent images in the message but the Conversational Cloud SMS connector does not support images. Therefore the consumer side failed to send the images and the bot agent received an empty message.
- The bot is configured to reply to a consumer only after receiving the consumer’s first message.
- The consumer typed too long a message (over 5000 characters). Therefore the consumer side failed to send the message content to the Conversational Cloud server and the bot received an empty message.
- Check network on consumer side
- Ensure images are supported
- Check configuration settings of the bot
- Ensure messages are less than 5000 characters
Starting a conversation consists of two separate requests (both sent from the consumer side).
- A request to open a conversation.
- The first message.
Our agent manager who has join agent conversations permissions is not able to see the option to join our bot’s chats. He goes to the Agents list and opens an active bot conversation. But he does not see the join option. This is because the join option is not available for bot chats. It is available for messaging conversations only.
See the join conversation button on the bottom of messaging window.
Check out our Developer Center for more in-depth documentation. Please share your documentation feedback with us using the feedback button. We'd be happy to hear from you.