Pull request check fails with internal error

Overview

CodeScene PR checks can occasionally fail with an 'internal error' message instead of returning analysis results. This article explains the common causes and how to resolve or work around them.

Symptoms

  • GitHub or GitLab check run shows a failure with the message 'internal error'

  • The check fails consistently on the same PR or intermittently across multiple PRs

  • No actionable analysis output is produced

 

Root cause

Internal errors on PR checks are typically caused by one of three things: a transient infrastructure issue on CodeScene's side (especially on cloud), a problem cloning or accessing the repository at the specific commit referenced by the PR, or an edge case in the code being analysed that triggers an unhandled exception in the analysis engine.

Resolution steps

  1. Re-run the check using the 'Re-run' button in GitHub Actions or GitLab CI. Many internal errors are transient and resolve on retry.

  2. If the error is consistent, check whether the PR includes any unusual file types, very large files, or binary files that might interfere with analysis.

  3. Check the CodeScene admin panel or application logs for error details tied to the check run timestamp.

  4. Verify that the CodeScene GitHub App or GitLab integration has read access to the repository and the relevant branch.

  5. If the issue is reproducible on a specific PR, contact support with the check run ID and the repository URL.

 

Prevention

Ensure the CodeScene integration has stable repository access. For self-hosted instances, monitor disk space and memory on the analysis worker — resource exhaustion is a common cause of internal errors on large PRs.