I’ve moved your post to a separate thread since in the case of the other thread, calls to https://sonarcloud.io/api/ce/submit were not succeeding with a 200.
This looks related to some functionality that was deployed very recently. I’ve flagged this thread for attention.
I’m investigating those 403 responses.
Could you tell me how the Sonar Token is configured on your build? Is it through the environment variable SONAR_TOKEN, or through a sonar.* command line property or some other way?
We are running this in an azure pipeline, so we add a “SonarCloud Service Endpoint” to the " Prepare Analysis Configuration" task. So we are not setting this explicitly ourselves.
Thanks for your answer, it is valuable information for us.
There is an issue on our side, a fix is in progress and should be deployed in the coming days.