Web, API & Performance

This section covers problems you may hit while using product features — recording, authoring, running tests, and reading results — across Web, API, and Performance. For login, account, access, and invite questions, see Frequently Asked Questions.

Web

• Recording isn't capturing my actions — the browser extension is disabled or missing permissions. Enable it, reload the page, and start a new recording session.
• Run is greyed out on a new testcase — save the testcase first; Run stays disabled while it is still being created.
• A local run ends the moment it starts — the Local Agent isn't connected. Launch it and confirm the connection indicator before running locally.
• A step fails because an element isn't found — the page changed or hadn't finished loading. Re-record the step or add a wait, then run again.

More detail in Recorder/local-agent issues and Recording.

Web step failures (and how to fix them)

• Click was intercepted by another element — a cookie banner, modal, or sticky header is covering the target. Dismiss/scroll past the overlay (add a step), then click.
• Element found but not interactable — the control is hidden, disabled, or still animating. Add a wait until it is enabled/visible before acting on it.
• Invalid selector — the locator's XPath/CSS syntax is malformed. Re-record the step or correct the locator expression.
• Stale element — the page re-rendered after the element was located. Re-locate the element on the current page state instead of reusing an earlier reference.

API

• Send or Run returns an error or no response — the endpoint URL, path, authentication, or headers are wrong or unreachable. Verify the request details and that the host is reachable.
• A variable from a previous step is empty — response extraction wasn't set or the earlier step failed. Check the extraction rule and the order of steps.
• Run won't start — the testcase isn't saved, or no Test Run Config is selected for a cloud run.
• 401/403 on a request that worked before — the auth token expired or the credential/secret changed. Refresh the token or update the auth configuration and re-run.
• SSL/certificate failure — the target uses a self-signed or untrusted certificate, or an internal host. Use a trusted endpoint or a reachable environment for the run.
• Request times out — the host is slow, unreachable from the runner, or behind a network/VPN boundary. Verify reachability from the execution environment and adjust the timeout.

More detail in Common run failures and Author Testcase.

Performance

• There's no functional testcase to select — create and save the API or Web testcase first, then pick it as the load source.
• Virtual Users or ramp fields are greyed out — JMX is selected, so those values come from the JMX plan rather than the form.
• My run stays QUEUED — cloud capacity or licenses are busy, or the requested Virtual Users exceed your plan limit. Wait for resources to free up, or reduce the load.
• Metrics or charts aren't showing — they appear only once the run is IN_PROGRESS, COMPLETED, ABORTED, or STOPPING — not while it is QUEUED.

More detail in Performance & load.