Replay & Configuration Issues¶

Test case won't replay successfully? This page covers replay failures, correlation errors, and configuration problems. Find the symptom that matches what you're seeing.

Quick Diagnosis¶

"Replay fails with 401 Unauthorized"¶

Symptom: Replay fails immediately or partway through with HTTP 401 errors.

Most common causes: 1. Authentication credentials missing or incorrect 2. Session expired between recording and replay 3. OAuth/Bearer tokens not configured for refresh

Fix: 1. Verify credentials: Check Actors View for username/password configuration 2. Run ASM wizard: May need to configure session tokens or authentication headers 3. Check for expiring tokens: OAuth/Bearer tokens may need refresh logic

See: Basic Authentication and OAuth & Bearer Tokens

"Replay fails with 403 Forbidden"¶

Symptom: Replay fails with HTTP 403 errors.

Most common causes: 1. Missing or invalid CSRF tokens 2. Incorrect authentication headers 3. IP-based restrictions (server expects different IP) 4. Session cookies not extracted from login response

Fix: 1. Run ASM wizard - Configure CSRF tokens as dynamic fields 2. Check session cookies - May need to extract session ID from login response 3. Verify IP whitelisting - If server restricts by IP, test from allowed IP range

See: Application State Management for correlation setup.

"Replay fails with 404 Not Found"¶

Symptom: Replay fails with HTTP 404 errors for URLs that worked during recording.

Most common causes: 1. URLs contain dynamic IDs that changed between recording and replay 2. Session-based redirects to different URLs 3. Base URL hostname changed (recorded from dev, replaying against test)

Fix: 1. Run ASM wizard - Look for session IDs, timestamp parameters, or unique IDs in URLs 2. Check for redirect changes - Server may redirect to different URLs based on session state 3. Verify base URL - Hostname may have changed

See: Debugging Failed Replays for detailed troubleshooting.

"Correlation error: Could not find expected value"¶

Symptom: Replay fails with error message about missing expected value.

What this means: ASM expected to extract a value (session ID, CSRF token) from a server response and couldn't find it. The response changed, or the extraction boundaries no longer match.

Fix: 1. Check the transaction that failed - Error View shows which page/transaction failed 2. Review extractor configuration - Fields View → find the extractor → check boundary strings 3. Check server response - Headers View or Content View → verify the value actually exists in response 4. Adjust extractors - Boundary strings may need updating if server HTML changed

See: Boundary Extraction for extractor configuration.

"Page content validation failed"¶

Symptom: Replay completes but validation shows unexpected content.

Most common causes: 1. Server returned error page but with HTTP 200 OK status 2. Server redirected to login page (session expired) 3. Server returned empty response 4. Dynamic field configuration missing

Fix: 1. Check Content View - Compare recorded vs. replayed response 2. Look for error messages - Server may return 200 OK but with error content 3. Check for redirects - Server may redirect to login page 4. Verify dynamic field configuration - Missing correlation may cause server to reject request silently

See: Debugging Failed Replays for content comparison.

"Connection refused during replay"¶

Symptom: Replay fails immediately with connection refused error.

Most common causes: 1. Server is down or unreachable 2. Firewall blocking outbound connections 3. Hostname/port incorrect in test case properties 4. VPN required but not connected

Fix: 1. Verify server is running - Try accessing in browser 2. Check hostname/port - Test Case Properties → verify target server 3. Check firewall - May need to allow outbound connections from Load Tester 4. VPN required? - Some environments require VPN to access test servers

"Some transactions succeed, others fail randomly"¶

Symptom: Replay succeeds sometimes but fails on specific transactions unpredictably.

Most common causes: 1. Timing issues (server needs time between requests) 2. Missing correlation for transaction-specific tokens 3. Server load balancer routing to different servers with different state

Fix: 1. Add think time - Increase delays between transactions 2. Check for transaction-specific tokens - Each transaction may have unique CSRF tokens 3. Verify load balancer session affinity - May need sticky sessions

See: Application State Management for correlation debugging.

"Page is being hit more than once per replay"¶

Symptom: Same transaction executes multiple times during single replay (duplicate requests).

Most common causes: 1. Browser auto-refresh or retry logic captured during recording 2. AJAX polling captured as multiple transactions 3. Browser prefetching URLs

Fix: 1. Delete duplicate transactions - Right-click → Cut in Test Case Editor 2. Disable auto-refresh during recording - Record with auto-refresh disabled 3. Use domain blocking to filter AJAX polling domains

See: Recording Settings for domain blocking configuration.

Configuration Problems¶

"Can't configure dynamic fields - ASM wizard doesn't detect anything"¶

Symptom: ASM wizard runs but doesn't find any dynamic fields to configure.

Most common causes: 1. Application doesn't use dynamic fields (rare) 2. Session already expired (replay fails before ASM can analyze) 3. ASM looking at wrong responses

Fix: 1. Ensure replay succeeds first - ASM needs successful replay to compare responses 2. Check for hidden fields - ASM detects form fields, URL parameters, JSON fields, cookies 3. Run replay twice - First replay may establish session, second replay will show differences

See: ASM Basics for ASM workflow.

"Missing user variables errors"¶

Symptom: Replay fails with errors about missing user variables or dataset fields.

Most common causes: 1. Dataset file missing or moved 2. Dataset column name changed 3. Dataset file empty

Fix: 1. Check dataset file exists - Datasets View → verify file path 2. Verify column names - Dataset column names must match field references 3. Check dataset has data - Open dataset file in spreadsheet, verify rows exist

See: Datasets & Data-Driven Testing for dataset configuration.

Error Message Lookup¶

Looking for a specific error message? Use the searchable error catalog:

See: Common Error Messages - Use Ctrl+F to search for the exact error text you're seeing.

Still Stuck?¶

If none of these solutions work:

Run the ASM wizard: Most replay failures are correlation issues - ASM Basics
Check detailed debugging guide: Debugging Failed Replays has step-by-step workflows
Contact Support: See Getting Support for how to gather diagnostic logs

Most replay failures are correlation issues: dynamic fields that ASM hasn't configured yet. Running the ASM wizard solves the problem over 80% of the time.