Analysis failing for a specific project

Overview

When analysis fails on a single project while others continue to run normally, the issue is almost always specific to that project's configuration, repository access, or data state. This article walks through the diagnostic steps.

Symptoms

  • One project shows repeated analysis failures

  • Other projects in the same workspace analyse successfully

  • The project admin page may show a red status indicator or error message

 

Root cause

Project-specific analysis failures are most commonly caused by: an expired or revoked repository access token, a branch that no longer exists or has been force-pushed, a repository that has grown beyond resource limits, or a corrupted analysis database entry for that project.

Resolution steps

  1. Open the project's admin page in CodeScene and review the most recent analysis log for a specific error message.

  2. Verify that the repository is still accessible with the credentials CodeScene holds, try cloning the repo URL manually with the same token.

  3. Check that the configured default branch still exists in the remote repository.

  4.  If the token has been rotated or revoked, update it under Settings → Integrations.

  5. If logs show a database or internal error, try resetting the project's analysis state from the admin panel (Analysis → Reset).

  6. If none of the above resolves the issue, contact support with the project ID and the full error log from the failed analysis.

Prevention

Periodically review project health in the CodeScene dashboard.