I have a DevOps project/repository that has a Build Validation pipeline that is used for pull requests (PR), along side this build validation is a SonarCloud quality gate status check.
In the SonarCloud project the Pull Request settings for the Provider has been set to Azure DevOps Services and a personal access token (PAT) set.
This project setup has been working where the quality gate and comments have been successfully working as expected, however this week the SonarCloud quality gate has now failed to recognise the SonarCloud analysis has been performed and no comments are added to the PR when they should have been.
The PAT has been checked and is set to Code R/W access and is valid into 2025. I have also performed a test and it can gained access to our DevOps organisation. This PAT has successfully been used in SonarCloud on many projects, but has suddenly stopped working.
I temporarily created another PAT with the same access and set the SonarCloud settings, this PAT works as expected.
I would prefer not to replace the original PAT as it is used in over 100 SonarCloud projects and it is also used elsewhere unrelated to SonarCloud.
Is there any reason why a PAT would become invalid in SonarCloud, but is a valid PAT?