Troubleshooting
Check the source, page state and permissions before retrying. Find the most useful diagnostic details without sharing private data.
Start with these checks
Check version and enhancements
These docs describe 1.1. Confirm your installed version, keep Enable toolkit enhancements on and refresh Kick after an extension update.
Check the owning source
The intended player and native chat must still be open. A replaced page can disconnect a live tool.
Check the relevant status
Use Player progress, Autoclipping Diagnostics, provider permission status or Ad blocker source status rather than repeating the button blindly.
Missing or overlapping controls
A player shortcut is missing in a small tile.
Wide-only controls such as speed and the delay badge are omitted when space is tight. Use Toolkit > Player for the corresponding controls. Check the feature toggle and actual native player availability.
Live rewind stops at a boundary.
Kick must offer usable DVR or a real downloaded buffer. A missing source cannot be replaced by an invented seek range.
A preferred resolution was not applied.
Check the offered native qualities and account access. Finish any open native settings menu; unavailable or locked choices cannot be forced.
A save or recording fails
Connection interrupted appears during a download.
Let the bounded retry finish. Cancel stops waits and requests. If retries are exhausted, keep the source available and prepare a new save after checking access.
A save waits for DVR.
The growing recording may lag live. The requested moment stays frozen; quick replay waits at most 45 seconds. If the required range remains unavailable, choose a newer or supported moment.
MP4 or WebM conversion is unsupported.
Try a supported format or Original source if you can use it. Protected sources, separate audio, encryption and browser codec limitations can prevent conversion.
The saved file cannot seek.
Ensure finalization completed before closing. For an earlier WebM with missing seeking metadata, try Player > Saved WebM > Save seekable copy.
Autoclipping finds nothing or too much
No moments appear.
Check selected open chats, new-message delivery, two-period warmup, thresholds, baseline, distinct chatters, cooldown/hour limits and queue capacity in Diagnostics.
Ordinary chat triggers too often.
Try Activity growth instead of a low fixed target. Increase meaningful baseline and distinct-author requirements, tune reaction phrases and test one change at a time.
One output succeeds and another fails.
Read their individual states. Saving and native publication have different ranges and timing constraints. Never repeat an uncertain public publication just to retry a file save.
Games, giveaways and alerts
A viewer's game answer was ignored.
Check the selected channel, an active round, exact answer command, per-game attempt limits and whether that message is new.
The detached giveaway window disconnected.
Keep the original source page open. After its reload, reopen the window from the current Toolkit. Export an explicitly labelled last received copy if needed.
Desktop mention notifications do not appear.
Check optional Chrome permission, the feature toggle, aliases, visibility conditions, shared cooldown and operating-system notification settings.
Send useful details
- Installed version, browser version and which tool failed
- The public channel/clip/VOD link, when relevant
- Main player or Multiroom tile, and the selected mode/format
- The exact visible error, the steps and whether it repeats
Written for version 1.1. Some controls may be unavailable in an earlier installed release. See release notes.