Virtual Agent don't start conversation

shun6
Giga Sage

Hi all

Recently my virtual agent stop working.

I think that when I created the script within the topic and check the movement, it took too much time to response so I end the conversation and remove that script.

After that, When I open the virtual agent, it shows like below image and don't start conversation.

Are there anyone who have any idea about this problem?

Thanks

 

find_real_file.png

1 ACCEPTED SOLUTION

Mark Roethof
Tera Patron
Tera Patron

Hi there,

Can you try to start the Virtual Agent web client without chat history? Is it working then?

Is it also only for your user? Or for all? And assume you reverted the changes mentioned?

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

View solution in original post

2 REPLIES 2

Mark Roethof
Tera Patron
Tera Patron

Hi there,

Can you try to start the Virtual Agent web client without chat history? Is it working then?

Is it also only for your user? Or for all? And assume you reverted the changes mentioned?

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

johndoh
Mega Sage

What was the resolution to this? I am seeing this issue in my environment even directly going to the web client without having the history turned on. It only seems to happen on some users.

 

I am currently testing https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827698 to see if it helps.

 

Currently the only thing that seems to resolve the concern is to have the users perform normal browser maintenance.