Why is my scan slow?

Learn why first-time Qodex scans take longer, what should get faster on rerun, and what to check when a saved run stays slow.

Why is my scan slow?

First-time scans are slower because Qodex is still learning and authoring.

During a first pass, Qodex may import endpoints, crawl pages, inspect flows, create scenarios, verify them, and save artifacts. After that work is saved, reruns should be much faster.

What to check first

What you see	Likely reason	What to do
A new API import or UI crawl takes minutes	Qodex is discovering and authoring tests	Let the first run finish, then compare the rerun.
The first UI replay is slow step by step	The replay cache is still warming	Run once successfully so Qodex can reuse stable actions.
Every request waits on the app	Target latency	Check staging response times, API logs, and CDN warmup.
All runs slow down together	Database or infrastructure load	Check Postgres CPU, locks, connection limits, and worker capacity.
Many sub-agents pause mid-run	Provider queue or high concurrency	Reduce scan scope or rerun later.

Exploration is different from replay

Exploration creates tests. Qodex reads the surface, decides what matters, creates scenarios, and verifies them.

Replay runs saved tests. API replay sends deterministic HTTP requests. UI replay uses saved browser actions and cached step resolution.

If the first run is slow and the second run is fast, Qodex is behaving normally.

API runs

Saved API scenarios do not need LLM calls during normal replay.

If an API replay is slow, the cause is usually the target API, network, database, or test environment. Check the endpoint timing before assuming Qodex is stuck.

UI runs

UI scenarios can be slower when the page changed or the replay cache is cold.

Once Qodex has a stable action for a step, it can run that action directly in Chromium. If the UI changes and the cached action fails, Qodex may use recovery to resolve the original intent again.

When to investigate

Investigate when a saved scenario or stable suite stays slow after a successful first run.

Do not worry if a first import, first crawl, or first scenario-authoring pass takes longer. That is where Qodex does the expensive thinking and setup.

Next steps

How Qodex works

See why discovery and replay behave differently.

Replay cache and self-healing

Learn how UI reruns get faster.

UI testing

Understand browser-driven testing.

LLM cost on reruns

See why reruns are cheaper than authoring.