Reproduction and authentication problems
Reproduction and authentication problems
Section titled “Reproduction and authentication problems”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.
ScenarioDeck does not silently fall back to the captured source system when replay cannot satisfy a required request.
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. Bind or re-authenticate the compatible local Persona, then choose Clean Session in the same Reproduce launcher and try again. 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 ScenarioDeck-owned browser session is using the profile, the managed browser cannot start, or the local profile needs recovery.
What to do: close other ScenarioDeck managed-browser sessions and retry. Use the Settings recovery/reset action only when ScenarioDeck reports that the Development Profile needs it. Never point ScenarioDeck 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. ScenarioDeck 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”ScenarioDeck 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.