Get a recording unstuck.

Recording will not start

Chrome cannot record this page

Switch to an ordinary website tab. Chrome protects internal pages, extension pages and the Web Store. Confirm the selected tab before starting.

The extension is missing or signed into the wrong account

Check the Chrome profile where you installed it. Pin Rill from the Extensions menu. To change Rill accounts, disconnect in the side panel, sign into the intended account and connect again.

Screen, microphone or camera permission was denied

Allow the needed browser and operating-system permissions, then try again. You can leave Mic and Camera off. Screen recording needs a supported desktop browser.

Saving or processing is stuck

A screen recording is still in preview

Keep the preview open. Download a local copy, then follow the recovery message or try saving again. Leaving before saving can lose the preview.

The upload is still running

Keep the recorder open and check your connection. Saving the upload and preparing playback are separate steps.

The upload is saved, but playback is not ready

Wait for the recording status to change. A queued recording is waiting for capacity; starting another take will not finish the first one. If an error appears, follow its retry guidance.

For a CLI recording, check its current status before retrying:

rill record status <recording-id>
# After an upload or encoding failure, from the original machine:
rill record retry <recording-id>

Retry needs the retained capture and original credential. Captures have a limited recovery window. See encoding and recovery details.

A link or account is not working

Someone cannot open the recording page

A private workspace URL does not grant access. Open the recording in the owning workspace and create a share link if you intend to share it.

A share link has expired

Ask the owner for a current link. Keeping a recording and keeping its share link active are separate settings. An expired, unclaimed anonymous recording cannot be recovered by connecting later.

A new connection points to the wrong workspace

Check which Rill account approved the connection. For a CLI agent, use rill whoami to inspect the current identity. Review agent access in Settings before changing it.

Your coding agent cannot record

Run these checks in the environment where the agent actually executes commands:

rill --version
rill --human doctor
rill whoami

Follow each failed check’s recovery instructions. The agent needs Node.js 22 or newer, Chrome or Chromium and browser tools that can attach to Rill’s browser over CDP. A desktop chat app may execute commands in a separate sandbox. Passing doctor does not prove the browser tool can connect.

Remote encoding does not require local FFmpeg. Local encoding does. For connection, keyring, network or browser problems, use the CLI troubleshooting reference. Avoid repeated installs when the environment cannot reach npm or Rill.

Get help

Contact Rill support with the recording ID or page URL, the recording method, the error text and the step where it stopped. Include your browser and operating system. Do not send passwords, tokens or a private recording to anyone you do not intend to grant access to.

If the recording shows the wrong tab or misses the steps you need, make a new take after fixing the selection. Reanalysis cannot recreate steps that were not recorded.