> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mindfort.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Retesting Findings

> Learn how to retest MindFort findings to verify a reported vulnerability has been fixed by revalidating it against the live target after remediation.

## Overview

Retesting verifies whether a previously reported red-team finding is still exploitable after you apply a fix. MindFort reruns the original security check against the live target and updates the finding with the result.

Use a retest after your team deploys a remediation. A retest focuses on the existing finding; it does not replace a full assessment when you need broader coverage of the target.

<Note>
  Retesting is currently available in beta for red-team findings. Each finding retest uses one credit.
</Note>

## Before You Retest

Confirm that:

* the remediation is deployed to the target environment
* the target is reachable by MindFort
* any credential required to reproduce the finding is still valid
* the finding is not already queued or being retested

If the original finding requires authentication, MindFort uses the credential configured for the target to prepare an authenticated session. You do not need to provide credentials again when starting the retest.

## Retest One Finding

1. Open **Findings** from the sidebar.
2. Select the target that contains the finding.
3. Open the finding details.
4. Click **Retest** in the finding actions.

The button shows the one-credit cost. After admission, the finding displays **Retest queued** and starts automatically when capacity is available.

## Retest Multiple Findings

You can queue several eligible findings from the same target:

1. Open the target's **Findings** view.
2. Select the red-team findings you want to verify.
3. Click **Retest Issues** in the bulk action bar.

MindFort reports how many retests were queued, skipped, or failed to queue. A finding is skipped when it is not eligible for a new retest, such as when another retest is already active.

To retest every open finding for a target, use the retest action in the findings toolbar. The credit indicator shows the number of open findings that will be submitted.

<Warning>
  Retest only after the relevant fixes are deployed. Starting the same checks before deployment consumes credits without validating the remediation.
</Warning>

## Understand Retest Status

The finding details show the current or most recent retest state.

| Status                        | Meaning                                                                                                    |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Retest queued**             | The request was accepted and will start automatically when a retest slot is available.                     |
| **Retest in progress**        | MindFort is validating the finding against the live target.                                                |
| **Confirmed fixed**           | The finding no longer reproduces. It moves to **Resolved**.                                                |
| **Still exploitable**         | The finding still reproduces. It remains **Active**.                                                       |
| **Retest couldn't complete**  | MindFort could not reach a security outcome. Review the displayed reason and try again after resolving it. |
| **Previous retest timed out** | The earlier run is stale. Start a new retest to get a fresh result.                                        |

A failed or incomplete retest does not mean the vulnerability is fixed. Only **Confirmed fixed** resolves the finding.

## Capacity and Queueing

MindFort limits concurrent retests so active checks remain reliable. If your organization is at capacity, the **Retest** action is temporarily unavailable. Wait for an active retest to finish, then try again.

Queued work starts automatically. You can leave the finding page and return later to review the result and completion time.

## Troubleshooting

If a retest cannot complete:

* confirm the target is online and reachable
* verify the remediation has been deployed to the tested environment
* update expired or changed [authentication credentials](/guides/authentication-credentials)
* check that login instructions still match the target's current flow
* wait for available capacity if the retest action is disabled
* start a new retest when the finding reports that the previous run timed out

If the issue continues, contact [support@mindfort.ai](mailto:support@mindfort.ai) with the finding ID and the failure reason shown in MindFort.

## Next Steps

* Review the complete [finding lifecycle](/guides/findings).
* Generate an AI-powered fix with [Patching](/guides/patching).
* Run a broader [assessment](/guides/assessments) when you need coverage beyond one finding.