The last successful analysis for us occurred on 5/22/2025, which was around the time we were informed that we would be automatically transitioning from a legacy SonarCloud plan to the team plan. Could this be related to that?
Also, after an analysis is complete, we get a link to check on the status. Clicking that link: https://sonarcloud.io/api/ce/task?id=xxxxx takes us to a page that says:
{
"errors": [
{
"msg": "Project doesn't exist"
}
]
}
Colin
August 11, 2025, 9:29am
2
Hey @Brad_Baker
I don’t think that it would be related.
If you’ve lost access to this project which is your organization, you can restore access using the Web API.
Hey there.
In SonarCloud, you must be granted project-level permissions to view a project, regardless of your organization-level permissions.
What you’re describing sounds like what happens when the permission template that gets applied to these new projects doesn’t grant the project creator permissions on the project, either through a group the project creator belongs to or the special Creators option in the permission template setup.
[image]
So, your first stop should be validating and fi…
I’m not entirely sure how it happened, but we ran into two separate issues:
The token in use didn’t have permissions for the project
We hit our maximum allowed lines of code (LOC), which caused the failure.
After generating a new token from an account with the proper project access and upgrading our plan, the problem appears to be resolved.
Thanks for your help!