Replay Troubleshooting¶
This page is the index for replay problems that aren't HTTP error codes. For status-code failures (401 / 403 / 404 / 400 / 405 / 500 / connection errors), the systematic methodology and per-error guides are in Debugging Failed Replays.
Most problems below have simple fixes: re-running a configuration wizard, adjusting a single setting, or accepting that some apparent differences (cookies, transaction counts) are actually correct behavior.
Try the AI Assistant First¶
The AI assistant has read-access to the same evidence you'd inspect manually: the Replay View, the Content View, the Headers View, the Errors View, and the lineage data on missing-variable errors. For most replay problems, asking the AI to look at the symptom is faster than working through a flowchart, and the answer is usually specific to your test case rather than generic. Open the AI panel (the AI icon in the toolbar or View → AI Assistant) and describe what you're seeing.
Useful Opening Prompts
For wrong-content cases:
My replay succeeds but the content looks wrong. The search results are
empty even though the HTTP status is 200 OK. Can you figure out what's
causing this?
For dataset cases:
For intermittent cases:
If the AI can't get you there, or if you'd rather work through the symptom yourself, the pages below cover each category by hand.
Pick Your Symptom¶
| Symptom | Page |
|---|---|
| Replay completes green but the content is wrong (login looks anonymous, search has no results, etc.) | Replay Runs But Shows Wrong Content |
| Cookie values in the replay don't match the recording | Cookies Differ Between Replay and Recording |
| Configured a dataset but replay always uses the same row | Dataset Values Not Being Used |
| Replay succeeds but takes 5-10x longer than the recording | Replay Is Much Slower Than Recording |
| Replay succeeds sometimes and fails other times with the same configuration | Replay Fails Intermittently |
| Replay has more or fewer transactions than the recording | Different Transaction Count Than Recording |
How-To Pages¶
These are configuration questions that sometimes come up while troubleshooting, even though they aren't really troubleshooting items:
| Question | Page |
|---|---|
| How do I change the username/password without re-recording? | Changing Username and Password |
| How do I replay every test case in a repository (e.g., for a nightly regression)? | Replaying All Test Cases at Once |
| How does the browser cache work during replay, and how do I simulate returning visitors? | Browser Cache Simulation in Replay |
Related Pages¶
- For HTTP error codes (401 / 403 / 404 / 500): Debugging Failed Replays
- To understand replay results: Understanding Replay Results
- For configuration: Application State Management, Authentication, Datasets