Skip to main content
Start with the symptom below. Keep the original capture or local recording files until you know whether the problem is recording, uploading, or playback.

The extension will not connect

Confirm the production build is installed, you are signed in to the intended account, and you selected a workspace where you are an owner or member. Restart Connect securely if the approval page is old. Keep the popup open until pairing finishes.

Recording does not start

Check the browser’s capture and microphone permissions, then confirm the selected source. Restricted browser pages may not allow capture or extension access. Try an ordinary website tab and refresh it after installing or reloading the extension.

Upload failed

Check connectivity and the error shown in the recorder. Do not discard a pending recording before reviewing recovery options. Confirm workspace permissions and monthly allowance if the server refuses the upload.

The video plays but chapters are missing

The original can become available before processing finishes. Wait for processing to complete, then refresh the capture. If the capture reports a processing failure, use its retry control. Silent recordings can have chapters; speech is required for a spoken transcript.

A transcript contains an incorrect phrase

Compare the text with the audio, then correct it using the capture’s editing controls. Background noise, overlapping speech, and unusual terms can affect recognition.

Playback buffers or quality choices are missing

Try Auto, a lower available resolution, or Original. Streaming variants may still be processing, and a smaller source will not have larger upscaled variants. If only one network fails, compare on another connection before re-recording. The link may have expired, been revoked, or point to a deleted capture. Ask the sender to check its status and send a current permitted link. Workspace-only access requires the appropriate membership.

A share has no console or network information

Check whether the sender chose Without DevTools. A content-only share intentionally omits diagnostic events. The source recording method and privacy policy can also limit captured context.

CLI upload says authorization is missing

Set the production endpoint and check the stored scopes:
Keep the login command running through browser approval. Local-server credentials are not production credentials. If record stop returns no public URL, inspect whether workspace sharing policy withheld it.

Report an unresolved issue

Include the action that failed, the exact non-sensitive error text, your browser or CLI version, and whether the problem repeats. Share private capture links only through the intended support channel. Do not include passwords, tokens, authenticator setup material, or recovery codes.