#047Tutorial1 min

Re-run an analysis after a fix

Return to Analyze with the project context, keep the checks and launch explicitly.

Hackaiz team · updated 18/11/2026

Illustration: two developers review a change before approving it.
Illustration: two developers review a change before approving it. Illustrative photo, not a screenshot.

01Why re-run

An applied fix must be verified. Re-running an analysis shows the finding is gone on the deployed version and that no new flaw appeared along the way.

02Steps

A re-run never starts on its own: you stay in control of what runs and is billed.

  1. 1Open the project’s report.
  2. 2Click Re-run analysis: you land on Analyze with the project context filled in.
  3. 3Check the target, connections and ticked checks.
  4. 4Launch the analysis explicitly.

03Reading the new report

Compare with the previous one: resolved, new or unchanged findings. If a finding persists, check that the fix was actually deployed and not just merged.

04Verifying a fix

A fix is marked verified only after replay, continuous integration and deployment verification. A new analysis alone is not enough to declare a fix verified; it does confirm what is observed today.

Tip: Wait for your deployment to finish before re-running, otherwise you analyze the old version.

Frequently asked questions

Take the next step

Was this article helpful?

Related articles