Troubleshooting
Common issues and how to resolve them. When in doubt, email support.
This page documents the issues we see most often and how to resolve them. If your problem is not listed, email support@brektra.com.
Scan stuck in queued
The scheduler ticks every minute. If a scan stays queued longer than two minutes:
- Check the Status page to see if the LLM proxy is operational.
- Re-confirm your target's DNS TXT record. Brektra refuses to launch scans against targets whose verification has expired.
- For local-execution scans, confirm the engine is connected in Settings → Engines.
Scan reports zero findings
Most often this means the surfaces you selected do not exist on the
target. An AI-surface scan against a static marketing site, for
example, will find nothing. Re-run with --surfaces=web,api or pick
the right surfaces in the UI.
If you expected an exploit and got none, switch to Aggressive Mode (on a target you own outright). Some findings require destructive proof to confirm.
Patch PR failed to open
- Confirm the GitHub App is installed on the repo. Settings → GitHub.
- Confirm the repo's default branch is reachable.
- For monorepos, the patch may target a path outside the repo's scope. Re-run patch generation against the specific package directory.
Re-test bypassed
The patch held against the original payload but the agent found an adapted variant. The new finding's replay shows the adaptation, and Exploit Memory now carries the variant for future runs.
CLI cannot scan localhost
The CLI's local mode probes /api/chat, /api/generate, /api/v1/chat,
and /chat by default. If your endpoint is at a different path, run a
verified-domain scan from the dashboard instead.
Email did not arrive
Check your spam folder for noreply@brektra.com. If still missing,
confirm your email in the workspace owner profile and email
support@brektra.com.