Recording and missing evidence
Find the cause of a failed capture or an incomplete recording.
Start with whether capture began, which page was in scope, and whether the evidence falls inside the retained interval.
Recording does not start
Section titled “Recording does not start”Use an ordinary application page. Chrome internal URLs, extension pages, and other protected surfaces cannot be recorded. Account-free recording also excludes local file URLs.
If Recorder is waiting for navigation, open an allowed application page or select Stop recording to cancel. For a connected project, confirm its domain and destination requirements and the selected issue state.
Browser debugging cannot attach
Section titled “Browser debugging cannot attach”Read the error shown in the panel. Organisation policies or another debugging connection can prevent attachment. Another extension’s embedded frame can also block recording on a page.
If the message identifies an extension conflict, try an approved clean browser profile or disable the conflicting extension for the test, then reload the page. Do not remove required organisation controls; ask your administrator when policy blocks access.
Earlier actions are missing
Section titled “Earlier actions are missing”Compare the missing action with the retained-timeline limit. The elapsed timer does not mean that the whole recording remains available.
Record a shorter checkpoint if needed. Save each segment before New recording and note the gaps in the execution summary.
Requests from another domain are missing
Section titled “Requests from another domain are missing”Check page and network scope. Local recording uses the starting hostname family; connected projects use their capture configuration. Clear viewer filters before concluding capture omitted the request.
Iframe values or targets are incomplete
Section titled “Iframe values or targets are incomplete”Check iframe trust rules, frame provenance, and component boundaries. Untrusted values may be masked, and closed Shadow DOM can limit target details. Missing values do not prove a field was empty.
Response bodies are unavailable or truncated
Section titled “Response bodies are unavailable or truncated”Check payload limits, content filtering, browser availability, and whether the response was streaming or binary. The viewer cannot recover a body the capture did not retain.
Capture stops unexpectedly
Section titled “Capture stops unexpectedly”If the debugger disconnects or the recording tab closes, inspect whatever stopped evidence remains and preserve it before resetting. Record the interruption and avoid presenting the session as a complete check.
For other symptoms, use downloads and generated tests or sign-in and submission troubleshooting.