Using a script on a webpage OR using developer tools, I am unable to get webchat to work.
I tried toggling The Web Chat Deployment setting on the org level, I tried switching between Basic and Modern and all modes give the same error. (included below)
Problem is, I am not specifying a user, I am setting a queue name
{status: 401, message: "404 - {"status":"GENERAL_RESOURCE_NOT_FOUND","code…lationId":"6f3d9f10-910a-11e8-acef-85ebb0a82cfd"}"}
message
:
"404 - {"status":"GENERAL_RESOURCE_NOT_FOUND","code":"GENERAL_RESOURCE_NOT_FOUND","reason":"Not Found","details":[{"errorCode":"GENERAL_RESOURCE_NOT_FOUND","fieldName":"user"}],"message":"Entity [user] is not found by id [ccdf116b-2335-4879-a200-a7c7427ee405]","correlationId":"6f3d9f10-910a-11e8-acef-85ebb0a82cfd"}"
status
:
401
Please note that in October, we will be removing the choice and deployments will be required for chat configuration. Today, you still have a choice but it's best to start transitioning over to leveraging web chat deployments.
I tried many times but, I am not getting the interactions using queueName after I disable the agentEmail. Please advice if any thing needs to be done in order to run it. And I have no errors in the code.
// Use getConfig.setConfigProperty() for any web chat configuration property to dynamically set config values.
webchat.getConfig().setData({
firstName: firstName,
lastName: lastName,
email: email,
You'll have to continue to troubleshoot it. Step one is using dev tools and seeing if that works. If it works, the issue is with your code. If dev tools doesn't work, it's likely that there's no agent on queue or the skills are mismatched or it's another configuration issue.
Sorry I was out of office or i would have replied quicker, in my case the issue was a delay of enabling the chat deployment. It showed enabled on the ui but didn't actually work until sometime later. No additional changes to our code but it worked that afternoon.