Last analysis has failed: ea7c5073-733c-4e47-aa9d-be4b274fff0a

SonarQube Cloud
1

Hi,

Since yesterday, 09/04/2026, we are receiving a “Last analysis has failed…ea7c5073-733c-4e47-aa9d-be4b274fff0a” when sonarqube cloud runs against our main branch of this public repo

I cannot see any logs indicating what the problem is, either in the github action or the SonarQube cloud UI.

Are you able to tell me what is causing the failure.

2

Hi,

Welcome to the community and thanks for this report!

Your analysis is failing because your repository contains a file with a path that exceeds SonarQube Cloud’s maximum component key length of 400 characters.

The problematic file path is 406 characters long:
spec/cassettes/TaskStatus_Validators_ProceedingsTypes/_valid_/with_proceedings/when_delegated_functions_question_has_been_answered_for_each_proceeding/and_emergency_certificate_is_used/and_emergency_defaults_question_has_been_answered_for_each_proceeding_and_is_false/and_the_emergency_level_of_service_has_not_been_answered_for_each_proceeding/1_2_2_4_3_2_1_1.yml

To resolve this issue, you have a couple options:

  1. Exclude the problematic directory from analysis (Recommended)

    Add this to your sonar-project.properties file or in your SonarQube Cloud project settings:

    sonar.exclusions=spec/cassettes/**
    This will exclude all cassette files from analysis. Since these are test fixtures/recordings, excluding them shouldn’t impact your code quality analysis.

  2. Rename/shorten the directory structure

    If you need these files analyzed, you could restructure the directory hierarchy to use shorter names or fewer nested levels.

 
Thx,
Ann

3

Many thanks and that makes complete sense.

Unfortunately i do not appear to have the privileges to do this, as i cannot see any project settings when logged in on the UI, but am checking with org peeps about this.

Are you able to confirm

a) that i do not have these permissions
b) whether using a sonar-project.properties would work in such circumstances (that i do not have privileges to do so via the UI). Ps: We used to have a sonar-project.properties file which excluded the cassettes directory but it, and other settings, never seem to have an affect.
c) whether the ministrypfjustice org settings do, in fact, prevent sonar-project.properties file having any impact at the repo level, and prevent project settings being accessible to lesser mortals such as myself.

Many thanks

Joel

4

Hi Joel,

If you don’t see it, you don’t have it.

Yes!

That’s worth digging into. What patterns did you use?

It doesn’t work that way.

 
HTH,
Ann