Troubleshooting
Last updated: Nov 13, 2026
The assistant does not review a pull request
Your code hosting platform shows no result and no comment, and the DevSecOps section of the group shows no row. Examine this list in this sequence.
| What you must examine | Where |
|---|---|
| On GitHub, the repository is inside the installation of the app | On GitHub, in the settings of the app |
| The connection shows Connected | Integrations, SCM connections |
| The toggle of the group is on, below Pull request review | Integrations, SCM connections |
| The repository is a Git root of that group | Scope section of the group |
| That root is Active | Scope section of the group |
| The group has an active Essential or Advanced plan | Group information |
If you change the target branch of an open pull request, the assistant starts a new review against the new branch. You do not have to push a commit.
The result is Incomplete
The scan did not end. Thus, some vulnerabilities can be absent from the result. The check reports a failure, because Fluid Attacks cannot tell you that your change is safe. The result does not tell you which part of the scan failed, because your action is the same in each condition.
On GitHub, push a new commit or ask for a re-run of the check. On Azure DevOps, there is no re-run. Push a new commit.
An Incomplete result is not a result about your code. If a re-run and a new commit do not change it, contact Fluid Attacks.
The check does not show a change
| What you changed | What changes the check |
|---|---|
| You granted or revoked an exception | Nothing. The platform publishes a new check run on the same commit. If it tells you that it could not update the check, push a commit or re-run the check on GitHub |
| The severity threshold | Ask for a re-run of the check. On Azure DevOps, push a commit |
| The exclusions of the root | Ask for a re-run of the check, or push a commit. On Azure DevOps, push a commit |
| The code | Push a commit |
The platform rejects an exception
If the platform cannot apply a grant or a revocation, it rejects it. Thus, it does not save a decision that your code hosting platform does not obey.
| Message | What you must do |
|---|---|
| Another exception now covers some of these vulnerabilities | Open the Exceptions tab. A vulnerability has one active exception at a time |
| The pull request was reviewed again and some of these vulnerabilities are gone | Open the review again and select the vulnerabilities of the newest result |
| The repository is not connected for pull request reviews | Connect the account again, and make sure that the toggle of the group is on below Pull request review |
| Exceptions can't be granted because the pull request is closed | Nothing. A closed or merged pull request does not accept an exception |
| Only the person who granted this exception can revoke it. Other Group Managers can revoke it once the grantor stops managing this group | Ask the person who granted it |
| This exception was already revoked | Open the review again. Somebody revoked it before you |
| This pull request is no longer available | The review is gone from the platform. Examine the DevSecOps section of the group |
Exception EXC-1 saved, but the check couldn't be updated now means that the platform kept your decision. But it could not connect to your code hosting platform at that time. To apply it, push a new commit or re-run the check on GitHub.
The platform rejects the connection
| Message | What you must do |
|---|---|
| Account already connected | The account belongs to another Fluid Attacks organization. Disconnect it there first |
| Connection refused. The installation could not be verified | Install the app again from GitHub |
| Connection not completed | Start one connection at a time. Click Connect SCM in the Fluid Attacks organization that must have it |
| Waiting for an owner's approval or Request sent to a GitHub owner | You are not an owner of the GitHub account. An owner must approve the request that GitHub sent to them by email |
| GitHub didn't uninstall the app, so the connection was kept | Remove the app on GitHub. Then, disconnect again |
| The app is no longer installed on this account, so the connection was removed | Somebody removed the app on GitHub. Connect the account again |
| This connection was already removed by someone else | Nothing. Another person disconnected it while you examined the list |
| Pull request review needs an active Essential or Advanced plan | Make sure that the group has an active Essential or Advanced plan. Then, activate its toggle again |
| The Fluid Attacks app is suspended on GitHub, so review cannot be turned on | Activate the app again on GitHub. Then, click Verify again |
| Update required | An administrator must approve new permissions on GitHub. The permissions that you gave before continue to operate |
| An SCM connection manages this credential, so it cannot be edited | Do not edit the credential. Manage the connection that created it in Integrations, SCM connections |
| An SCM connection manages this credential. To remove it, disconnect the account | Do not delete the credential. Disconnect the connection that created it in Integrations, SCM connections |
The check is necessary, but GitHub lets you merge
The check reports the same result for a clean pull request and for a pull request that passes with exceptions. A branch protection rule cannot see the difference. For the configuration, read GitHub.
Also, make sure that you attached the check to the Fluid Attacks Platform app in your ruleset. Thus, no other app can report the check in its place.
Azure DevOps: the connection is rejected
| What you see | What you must do |
|---|---|
| The sign-in does not accept your account | The organization must belong to a Microsoft Entra directory, and you must sign in with a work or school account of that directory. A personal Microsoft account cannot connect |
| Entra answers Need admin approval | A Global Administrator of the directory must approve the Fluid Attacks application one time |
| The setup stops and asks for an administrator | Your account is not a Project Collection Administrator of the organization. Only that role can give the Git permissions |
| The organization belongs to another organization | An Azure DevOps organization connects to one Fluid Attacks organization. Disconnect it there first |
| Azure DevOps refuses the Fluid Attacks app, so review cannot be turned on | Activate the Fluid Attacks application again in Microsoft Entra. Then, click Verify again |
Azure DevOps: a repository does not appear when you add repositories
An older connection does not show the projects that you create after you connect the organization. Its card shows Update required. Click Connect SCM again on the same organization. You do not have to disconnect.
Azure DevOps: the status does not block the merge
The status alone does not block a merge. Add a Status check policy on the target branch.
Open Repos, Branches, the More options icon of the
branch, and Branch policies. Below Status checks, select +. Choose
the status fluidattacks/peer-reviewer-assistant. Set Policy requirement
to Required. For more information, read Block the merges that disobey your
policy.
To edit the policies of a branch, you must belong to the Project Administrators group, or have the Edit policies permission of the repository. This is not the same role that connects the organization.
GitLab: the integration does not operate after the setup
After the integration setup, the merge request (MR) shows a comment that tells you that the analysis started. If the MR does not show this comment, connect the integration again. Do these steps:
- Go to Integrations > Workflows on the Fluid Attacks platform.
- Find the GitLab Peer Reviewer Assistant card.
- Click the Edit button (or the related management button) for the connected group.
- Disconnect the current integration in the Manage GitLab Peer Reviewer Assistant Integrations window.
- Do the integration setup again from the start:
- Click the Use integration button.
- Select the group.
- Click Connect.
- Authorize the GitLab connection.
- Configure the integration (GitLab project).
- Click Update to complete the setup.
This procedure refreshes the integration tokens and the webhook configuration. Thus, the Peer Reviewer Assistant can analyze MRs correctly.
GitLab: token expiration and renewal
The integration tokens of the GitLab Peer Reviewer Assistant expire after 6 months. After this period, the integration stops, and you must renew it.
To renew the integration, do the steps in GitLab: the integration does not operate after the setup. Disconnect the current integration and do the setup again.
Fluid Attacks recommends that you set a calendar reminder 6 months after the first integration setup. Thus, the security analysis continues without interruption.
Azure DevOps Peer Reviewer Assistant
Connect your Azure DevOps organization, select the groups that get their pull requests reviewed, and manage or disconnect the connection.
Use a configuration file
Learn to use configuration files for vulnerability scans with the Fluid Attacks scanners. Fluid Attacks offers SAST, SCA, DAST, CSPM and MAST security analysis.