Skip to main content
A retest re-runs the specific vulnerability against your app to check whether it’s still reproducible. After you ship a fix, a retest is the fastest way to confirm the agent can no longer exploit the issue.

​
Retesting a single finding

Open the finding’s detail view and click the Retest button in the top right. The agent replays the exact attack it used when it first reported the finding, against your latest deployed code. The result either comes back as still reproducible (the finding stays Open) or no longer reproducible (the finding flips to Fixed).

​
Bulk retesting

On the dashboard you can select multiple findings and run retest on all of them at once. Useful after a release that touches a lot of code, or when you want to sweep through everything that’s been sitting Open for a while.

​
Adding retest instructions

Before kicking off a retest, you can give the agent additional instructions. Things like ‘I added input validation on /api/users, please confirm injection via that parameter is no longer possible’ or ‘the fix shipped in v2.4.1, please verify against that build’. The agent uses your instructions to steer the retest, so it focuses on exactly what you want confirmed. This works for single retests and bulk retests.

​
Automatic status updates

Once a retest finishes, the agent updates the finding status for you. If the vulnerability is no longer reproducible, the status flips from Open to Fixed automatically. If it’s still reproducible, the finding stays Open and the retest result lands in the Activity tab with whatever the agent observed. Either way, you don’t have to mark anything by hand.