Replay and authentication problems
Replay and authentication problems
Section titled “Replay 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, or its response was intentionally unsupported.
What to do: inspect the safe target list in Live Session, confirm the application is on the intended route, then either recapture the required supported request or explicitly route the selected dependency to Local. Do not add a broad remote allow rule to hide the miss.
Clean Session requires authentication
Section titled “Clean Session requires authentication”Likely causes: the State Card declares a Persona without a compatible local binding, or a saved session expired.
What to do: inspect the card’s Persona status. Bind or re-authenticate that Persona on this machine for the exact project and frontend origin. A Development Profile login alone does not make a portable Clean Session binding.
Development Profile is unavailable or locked
Section titled “Development Profile is unavailable or locked”Likely causes: another ScenarioDeck process is using the owned profile, or the managed browser cannot start.
What to do: close other ScenarioDeck managed-browser sessions, then retry. Do not point ScenarioDeck at your normal Chrome profile.
A card is not Verified
Section titled “A card is not Verified”Likely causes: it was opened in Development Profile, the run was incomplete, or replay/auth checks failed.
What to do: reopen the exact card in a Clean Session and resolve the reported safe miss or authentication status. Only Clean Session can produce Verified.