Background task fails, postgres error Integer out of range


I just added the Sonar config with the location of the frontend code in addition to the backend code. This worked fine in the branch. After merging the master branch analysis triggers but that background task fails with an

### Error updating database.  Cause: org.postgresql.util.PSQLException: ERROR: integer out of range
### The error may exist in org.sonar.db.component.ComponentMapper
### The error may involve org.sonar.db.component.ComponentMapper.insert-Inline
### The error occurred while setting parameters
### SQL: INSERT INTO projects (       organization_uuid,       kee,       uuid,       uuid_path,       project_uuid,       module_uuid,       module_uuid_path,       main_branch_project_uuid,       name,       long_name,       qualifier,       scope,       language,       description,       private,       tags,       root_uuid,       path,       copy_component_uuid,       enabled,       created_at,       b_changed,       deprecated_kee,       b_copy_component_uuid,       b_description,       b_enabled,       b_language,       b_long_name,       b_module_uuid,       b_module_uuid_path,       b_name,       b_path,       b_qualifier     )     VALUES (     ?,     ?,     ?,     ?,     ?,     ?,     ?, 

My setup:
Single Gradle project with sub projects for backend (Java) and frontend (Angular (typescript)). I cannot find any further information on how to proceed.
In case a SonarCloud admin is reading. The analysis id is: AYlD_XGGc65H51gRvNUI


I’m getting similar issues.

I deleted the project and when I try to recreate it (UI), it fails with this message: “Could not provision some of the projects (0/1)”

Trying to push from the command line I get:

  • What went wrong:
    Execution failed for task ‘:sonar’.

Failed to upload report - An unexpected error occurred. Please try again later.

I am facing this issue also for the .NET project.

1 Like

Hi Sven,

Thanks for the reply, but Could not provision seems a different issue, I would expect this to be an issue with a delete not being processed.

Same issue here, none of our pipelines in Azure DevOps are working anymore.

1 Like

Yep same here. C# .NET using DevOps pipelines

Hello everyone,

Thank you very much for the reports. We have opened a major incident and our engineering team has identified the issue and working on a fix.

Updates will be provided also here:


Considering the comment below, the issue seems to be the same.

I suspect someone used a “serial” for a sequetial generated id instead of a “big serial”

you’re right, at first glance it seemed unrelated since the error was different

same issue here! any solutions yet?

The issue has been resolved. Please test and provide feedback.

Best regards,

1 Like

Yes, everything works again for me. Thanks

Problem is resolved, thanks!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.