Inactive integrations and project items
An integration (Named Configuration) or a project item can appear as inactive. In that state, verification runs (scans) do not run successfully until the underlying problem is fixed. The UI shows that the integration or project item is inactive, or that the run cannot start.
Inactive integration (Named Configuration)
The platform connection is not usable for scanning until it is healthy and active again.
Typical causes:
| Cause | Description | Solution |
|---|---|---|
| Expired API token | The PAT or GAT reached its expiry date. | Create a new token in your platform that should be integrated, update the integration in KvantumCI (under User - Integrations in the left sidebar menu) with the new token, then activate manually the integration again. This manual activation is used for safety reasons. |
| Insufficient token permissions | The token was rotated or edited and no longer has the scopes KvantumCI needs, or access was revoked at the provider. | Restore the required permissions or replace the token, then activate manually the integration again. |
| Manual deactivation | Someone disabled the integration. | Turn it back on from Integrations when it is safe to do so. |
Inactive project item
A project item points at a specific Named Configuration, repository, and branch. It can become inactive even when other lines on the same project are still active.
Typical causes:
| Cause | Description | Solution |
|---|---|---|
| Parent integration is inactive | Note: see possible reasons here | Fix the Named Configuration first; project lines that depend on it stay inactive until the integration is active again (refresh the project page if needed). |
| Branch deleted or renamed on your integrated platform | The branch this line was bound to no longer exists under the same name. | In the project, add or select the correct branch for that repository, then update the project item (or remove the inactive project item and Add → Project Item again with the new branch). |
| Repository renamed or moved | The slug or path at the provider no longer matches what KvantumCI stored. | Update the integration’s repository selection within the project, or remove the old project item and attach the repository again under its new name. |
Prevention
-
Track token expiry and rotate credentials before they lapse.
-
After renaming repositories or branches in the integrated platforms (e.g. GitHub, GitLab, Bitbucket, Azure DevOps...), reconcile Integrations and Project Items so names and branches still match reality.