Troubleshooting

The short list of things that actually go wrong, and what each one means.

The launcher doesn't appear

  • Open the browser console on the page. The widget logs its problems prefixed with [BugClip] — e.g. Missing data-project-key on the script tag means the attribute was dropped in the paste.
  • Check the snippet is present and the src URL actually loads (open it in a new tab — you should see JavaScript, not a 404).
  • If the key is wrong or the project was deleted, the widget fails quietly by design — re-copy the snippet from the project's Widget settings.

“Nothing happened when I clicked record”

The reporter dismissed or denied the browser's screen-share prompt. Nothing can be captured without it — ask them to try again and allow sharing. On mobile browsers the prompt never appears because screen capture isn't supported there.

Reports upload but never reach Slack

  • Use Send test message in Widget settings first — it isolates the webhook from everything else.
  • Slack delivery is Pro: on the Free plan the webhook is kept but paused. Check Billing.
  • If the webhook was revoked in Slack, saving a fresh URL fixes it.

A report has no Technical context section

  • The workspace was on the Free plan when it was uploaded — context is discarded at upload, so upgrading later can't restore it for old reports.
  • Errors that happened before the page loaded the widget aren't in the buffers — the widget can only see what happens after it installs.

“Recording is too large”

Uploads are capped at 100 MB — several minutes of video. For long reproductions, a shorter clip of just the failing step plus a note beats a ten-minute tour.

Can't create a second project

The Free plan includes one project. See Plans & billing.