Hi guys - we've hit a weird issue:
In Dev we have a working instance of Connect Chat. It had previously been migrated to test, but we decided to roll back use of the module until we were were comfortable with the functionality. WE had basically set up a Chat button on Service Portal which would launch a connect chat window for a specific Chat Queue. We turned off this widget in the meantime.
We subsequently made some changes in DEV chat_queue records (modified some names and relationships to Assignment groups - nothing which should ostensibly affect the Connect module - and then migrated the new groups and the updated Widget back to TEST.
We now find that we get odd behaviour and can't launch the queue chat. When we trigger a chat with the queue from a user, we see the badge and "Accept" button appear for the Operator:
When the Operator clicks the Accept button, nothing happens - however in the back-end we can see that the chat_queue_entry record is being set to "Accepted" and assigned to the correct user. For some reason though, the operator doesn't see the chat window appear on their screen.
When the Operator clicks for a second time on the Accept button, they see the following error message "the queue is currently empty":
We see the same behaviour when we go to the direct chat link for ANY of the chat_queue records we have in the system.
When we look at the browser Console we see a 404 error on the Connect API itself once the second click has happened (likely because the queue has been addressed):
Any thoughts? This has us scratching our head.
