Troubleshooting¶

Most workflow sections have their own troubleshooting subsections inside their main topic pages, because the fastest path to a fix is finding it next to the procedure that failed. This section is the catch-all: error messages and failures that don't belong to any one workflow phase, plus the cross-cutting issues users hit most often. If you know exactly what step is failing, the troubleshooting subsection inside that workflow page is usually faster. If you're not sure, start here.

In This Section¶

Common Errors: Error messages that appear across multiple workflow phases, indexed by message text so you can find yours by searching.
Recording Issues: Chrome extension problems, debugger detachment, missing transactions, and other recording-side failures.
Replay & Config: Cross-cutting replay and configuration failures: orphan variables, ASM stale state, extractor materialization issues.
Load Testing: Failures that surface only under load: engine crashes, connection exhaustion, rate limiting, license cap hits.
Cloud & Engines: AWS-side problems: IAM permissions, region availability, engine provisioning timeouts, network connectivity to the test target.
Getting Support: When the docs and the AI don't get you unstuck. How to collect diagnostic logs and what information to include when you contact Web Performance support.

For most problems, start with the workflow-phase troubleshooting next to the step that failed. Come here when the failure spans phases or you can't tell which phase is failing.