Connect Support Closes chat immediately

josephtucker
Giga Contributor

When trying to implement connect support in ServiceNow, I've added a link to a chat queue in the left navigation menu. I've set this up similar to this:

find_real_file.png

When a user attempts to start a support chat, the chat immediately closes indicating "You have closed this support session"

Why would this be happening and how can I prevent this from occurring?

Thanks

1 ACCEPTED SOLUTION

andersba
Giga Contributor

In our case, we had to change the default value of State on the chat_queue_entry table.   It's supposed to be 1 (open), but we had changed the default value on task to -5 (pending), so we needed to override that on the child table.


View solution in original post

5 REPLIES 5

Jae Delaney
Kilo Contributor

EDIT: So it's doing it in two instances related to my group but not in my personal dev instance. I will investigate to see what might be causing the issue on my group's instances that is different on my own dev instance tomorrow when I get into work



I noticed this on an instance I was working in recently, started from scratch in a different instance and got the exact same result. For more context, it was working on all instances (we run Geneva) as of the 11th, and the first time I noticed an issue is yesterday (fortunately, we're still testing this feature, it isn't actively in use yet. But as I said, in two instances, if you're an end user, your chat session automatically closes as soon as it opens and cannot reconnect, giving you an error that says it's trying but never changes. It doesn't let you enter anything else into chat, and it doesn't show that there is a person in the queue from the analyst side, but in the Queues section as an admin, it shows the person as Waiting in the Chat queue entries. Here is a screenshot of what happens as soon as you try from an end user perspective, with the important sections marked in red.


Connect Support Issue.png


Did you ever find out what was causing the error here?   We're experiencing the same problem on our instances.


Was the solution found for this ?


andersba
Giga Contributor

In our case, we had to change the default value of State on the chat_queue_entry table.   It's supposed to be 1 (open), but we had changed the default value on task to -5 (pending), so we needed to override that on the child table.