Troubleshooting

Last updated: Feb 5, 2026

Integration not working after setup

If, after completing the integration setup, you do not see a comment in the merge request (MR) comments indicating that the analysis has started, you may need to reconnect the integration. Follow these steps:

1. Navigate to the Integrations section on the Fluid Attacks platform dashboard.
2. Locate the Gitlab Peer Reviewer Assistant card.
3. Click the Edit button (or the corresponding management button) for the connected group.
4. In the Manage Gitlab Peer Reviewer Assistant Integrations window, disconnect the current integration.
5. Repeat the integration setup process from the beginning.
   • Click the Use integration button.
   • Select the group and click Connect.
   • Authorize the GitLab connection.
   • Configure the integration details (GitLab project and assignee).
   • Click Update to finalize.

This reconnection process will refresh the integration tokens and webhook configuration, ensuring that the Peer Reviewer Assistant can properly analyze MRs.

Token expiration and renewal

The integration tokens used by the GitLab Peer Reviewer Assistant have a 6-month validity period. After this period, the integration will stop functioning and will need to be renewed.

To renew the integration:

1. Navigate to the Integrations section on the Fluid Attacks platform dashboard.
2. Locate the Gitlab Peer Reviewer Assistant card.
3. Click the Edit button for the connected group.
4. Disconnect the current integration.
5. Follow the complete integration setup process again (as described in the initial configuration steps).

It is recommended to set a calendar reminder 6 months after the initial integration setup to ensure continuous operation of the security analysis.