Reproduction and authentication problems
Reproduction and authentication problems
Section titled “Reproduction and authentication problems”A run completed but the result is not confirmed
Section titled “A run completed but the result is not confirmed”Browser and session completion report lifecycle, not whether the selected saved state was reached. Use the terminal status and its one primary reason. A partial, not-confirmed, failed, unsupported, cancelled, or user-rejected result must not be treated as success.
Expand Replay warnings in the run result or Latest run to inspect individual request changes. The badge counts unresolved request changes; collapsing the list does not change the result. A Journey reaching 100% means its actions finished, while the terminal result also checks restoration and replay evidence.
For an older run, Result not classified by this version means its readable evidence predates trusted qualification. Reproduce the exact State Card revision again when you need a current result; the older lifecycle is never upgraded to confirmed.
The CLI reports REPRODUCTION_OUTCOME_UNAVAILABLE
Section titled “The CLI reports REPRODUCTION_OUTCOME_UNAVAILABLE”The interactive Journey adapter reached its bounded deadline before it could
read the persisted terminal result. This is an adapter availability result, not
a reproduction outcome. It exits with code 5 and intentionally has no
outcome status, primary reason, or receipt.
Return to the State Card’s Latest run or retry the supported operation. Do not interpret the adapter timeout as confirmed, failed, or cancelled machine evidence.
A request is reported as a replay miss
Section titled “A request is reported as a replay miss”Likely causes: the request was not captured, its occurrence sequence changed, the current code now requests something new, or the dependency is outside the supported captured scope.
What to do: inspect the State Card’s Network evidence and Latest run, confirm that the current application is on the intended route, then either recapture the required supported request or explicitly route the supported dependency to an approved loopback Local target. Do not add broad remote access merely to hide the miss.
StatePort does not silently fall back to the captured source system when replay cannot satisfy a required request.
Captured source stops on a request
Section titled “Captured source stops on a request”Likely causes: a saved page, Chrome Capture’s current application code, or a legacy current source shell requested data that was not captured, or it attempted a mutation.
What to do: inspect the safe request evidence and Network → Details, or choose Local app for current code. A Card with eligible retained page material serves its saved page without contacting production. Chrome Capture does not archive application code and loads the current site from its exact source origin; compatible legacy Cards may also use a current source shell. Recapturing with the Chrome extension does not create an offline-code guarantee. In every path captured API data takes precedence and unmatched data requests remain blocked. See the source boundary.
Clean Session requires authentication
Section titled “Clean Session requires authentication”Likely causes: the State Card declares an Auth Persona without a compatible local binding, the saved local authentication expired, or the current machine has no approved authentication for that origin.
What to do: inspect the Card’s authentication status and use its available Persona selection or sign-in recovery. For a separate local app with no compatible Persona, record a new managed Capture at that exact origin, sign in, and save the detected Persona through Review. Then return to the original Card and select it when offered. See Personas and bindings. Development Profile login state is machine-local and is not silently copied into Clean Session or an ordinary share.
A protected local value is required
Section titled “A protected local value is required”Likely cause: the Card was saved with a supported protected value retained on this device.
What to do: explicitly authorize the protected value for this reproduction run when the launcher offers that choice. Consent is per run and does not become a permanent portable setting.
If you need an ordinary credential-free share instead, use a State Card that was saved after the creator confirmed Discard for that value; the corresponding Journey step becomes a manual barrier.
Development Profile is unavailable or locked
Section titled “Development Profile is unavailable or locked”Likely causes: another StatePort-owned browser session is using the profile, the managed browser cannot start, or the local profile needs recovery.
What to do: close other StatePort managed-browser sessions and retry. Use the Settings recovery/reset action only when StatePort reports that the Development Profile needs it. Never point StatePort at your normal Chrome profile as a workaround.
A Recorded Journey pauses
Section titled “A Recorded Journey pauses”A Partial Journey contains an explicit manual barrier. This is not the same as a crash or an automatic step failure.
Complete the requested manual step in the managed browser, then choose Resume. StatePort continues with the later recorded automatic segment only after that explicit handoff.
Reproduce stops on a missing or ambiguous target
Section titled “Reproduce stops on a missing or ambiguous target”StatePort resolves recorded actions by exact semantic meaning. If the current application no longer contains one exact compatible target, the Journey stops instead of guessing with a fuzzy selector, coordinate, XPath, or CSS fallback.
Check whether the current code intentionally changed the UI. Use Saved state when it remains useful, or recapture the workflow when the recorded semantic path no longer matches the application.
Verification evidence is unavailable or failed
Section titled “Verification evidence is unavailable or failed”A Development Profile run and a Clean Session are different browser-session choices in the same Reproduce workspace. Existing verification evidence, where present, belongs to the exact revision and recorded qualifying conditions; it is not a promise that all future current code will reproduce identically.
When a clean reproduction fails, use the typed current-run evidence—such as target readiness, replay miss, authentication, or compatibility status—rather than treating the old State Card as silently corrupted.
The app closes after an unexpected internal error
Section titled “The app closes after an unexpected internal error”Reopen StatePort and check your Library. Already saved State Cards remain available. If a stopped capture has a recovery entry, open it to review what was saved. Work that had not reached durable storage may need to be captured again. StatePort does not automatically save an unfinished capture or mark an interrupted reproduction as confirmed during an unexpected shutdown.