Use this page to diagnose common connection and answer problems. For the message contract, see Handle server messages.
The connection returns HTTP 403
The website origin is not registered for the DXP Organization. Confirm that the browser is connecting from the expected domain and ask your Squiz account team to verify the DXP Organization’s registered domain configuration.
The connection returns HTTP 404 or is refused
Check that:
- the endpoint uses
wss://; - the region and DXP Organization ID are correct;
- the chatbot ID identifies an enabled agent;
- the URL includes
/ws/v2/; and - the endpoint matches the deployment approach for your site.
The answer appears only at the end
Inspect the WebSocket messages in your browser’s developer tools. If delta messages are present, update the interface after every delta rather than waiting for response. If no deltas are present, use response.answer as the fallback. Also confirm that the client connects to the configured endpoint and that an older built client is not being served by a cache.
A follow-up loses its context
Confirm that the client saves threadId from info, delta, or response and includes it in the next chat message. A new WebSocket connection starts a new session. If the connection was lost, tell the visitor that a new conversation has started.
A partial answer remains after an error
Clear the per-turn buffer and remove or replace the partial assistant message when an error occurs. Ignore only errors whose step is cancelled.
Other errors should end the current turn and present a safe retry message.