Template for a good new topic, formatted with Markdown:
ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
Github
CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI
Azure DevOps
Scanner command used when applicable (private details masked)
N/A
Languages of the repository
.NET
Only if the SonarCloud project is public, the URL
N/A
And if you need help with pull request decoration, then the URL to the PR too
N/A
Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
When trying to create a project via any means either manual, importing the repository or setting up a mono repo the following error occurs, this has been happening for over a week now.
{"errors":[{"msg":"An unexpected error occurred. Please try again later."}]}
Steps to reproduce
Analyze new project, manual, import and monorepo - all fail
Definitely logged into both Github and Azure DevOps and yes this is using the UI, I picked the JSON error out of the browser network trace when trying to investigate the failure, but itâs not a very helpful error
So for one of the three methods Iâve tried I simply go to âAnalyze new projectâ, my list of repositories loads fine, I select the one Iâm trying to set up and click Set Up. This is what throws the above error.
This also happens if I select the Monorepo feature and strangely enough also for the Manual setup which has nothing to do with a specific repository.
Apologies for the delay. Could you try again and tell me which API endpoint returns the {"errors":[{"msg":"An unexpected error occurred. Please try again later."}]} response?
Could you also let me know at what time youâve performed the API request, so that I can easily find it in out logs.
Thanks. The issue is that your new project matches two permission templates that are defined in your organization. A project should only match at most one permission template.
Can you have a look at the Project key pattern of your permission templates? You can find this under Organization > Administration > Permission templates
Of course the error message you got was not helpful at all, weâll improve it on our side.