> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connectly.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Troubleshooting
> Diagnose the quiet failures — an inactive client key, two integrations on one page, a server-side import, or a framework that will not render the element 🔧
This widget is being rolled out. Interfaces on this page may change before general
availability. The engineering documentation site, which tracks the current build, is at
[webchat.connectly.ai/docs](https://webchat.connectly.ai/docs/).
The widget fails quietly more often than it fails loudly, which is what makes these worth
naming.
## The launcher appears, but chat does not work — or it looks unstyled
**Check the client key first.** An unrecognized or revoked key makes the widget fall back
to a default appearance and fail to start a conversation, *without* stopping the launcher
from rendering. So a launcher on the page proves the script loaded; it proves nothing
about the key.
Turn logging up (below) and look in the console for a warning naming the client key, or a
"widget config unavailable" / "unknown or inactive" message.
## A key I just created looks broken for the first minute
Expected, not a bug. A newly issued key can take **up to 60 seconds** to become active
everywhere, and a revoked key can likewise take up to 60 seconds to actually stop working.
Wait a minute and reload before concluding the integration is wrong — and do not treat a
revocation as an incident response tool on its own.
## npm cannot install the git URL
If HTTPS asks for credentials, the two variants that usually help:
```sh theme={null}
# A developer machine set up with an SSH key rather than a token:
npm i git+ssh://git@github.com/connectlyai/webchat.git#v1.1.0
# CI, with a token in the environment and no interactive prompt available:
git config --global url."https://x-access-token:$GITHUB_TOKEN@github.com/".insteadOf "https://github.com/"
```
`Repository not found`, or a credential prompt that will not take your password, almost
always means the token lacks read access to the repository — not that the tag is wrong.
## Two launchers, or a transcript that splits in half
You have two integrations on one page — almost always the paste-in `