Last analysis failed: 9b728abf-9167-43bd-acac-14f703f50b59

[m1kkel (Michael Neto)]

• We work on GitHub
• We used GitHub Actions for our CI and our CD.
• Project uses Typescript (React), python, javascript, dockerfile
• GitHub - COS301-SE-2026/AutoFlow-Trade-Simulator · GitHub
  • Resolved an error with removing old container since the variable was … by u24574547 · Pull Request #314 · COS301-SE-2026/AutoFlow-Trade-Simulator · GitHub

• Last analysis failed: 9b728abf-9167-43bd-acac-14f703f50b59
  

I do not know whether or not this is the appropriate way to receive support for our issues. The quality gate still passes, we just think that this is causing our successful build % to decrease.

[stevan.vanderwerf]

Hi @m1kkel,

I looked into analysis 9b728abf-9167-43bd-acac-14f703f50b59 for PR #314. The failure is expected behavior, not a bug.

Two analyses were submitted for the same PR. By the time this one was processed, a newer commit’s analysis had already been recorded. SonarQube Cloud won’t process an older commit’s report after a newer one has already landed. Doing so would roll back analysis results.

This can happen after a force-push to the PR branch. A CI run triggered by the original commit was still queued, and its report arrived after the updated commit’s analysis had already completed.

Your quality gate is unaffected, the successful newer analysis already set the result correctly. The only visible impact is the failed analysis count you noticed in your build statistics.

To avoid these failures going forward, you can configure your GitHub Actions workflow to cancel in-progress runs when a new push arrives:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

This ensures only the latest commit’s analysis runs, and older in-flight jobs are cancelled before they submit a stale report.

Hope that helps.

Best regards,

Stevan