# Pull Request Failure

**URL:** <https://community.sonarsource.com/t/pull-request-failure/112201>\
**Category:** SonarQube Cloud\
**Tags:** sonarqube-cloud\
**Created:** [March 27, 2024, 7:17pm UTC](https://community.sonarsource.com/t/pull-request-failure/112201 "2024-03-27T19:17:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwexler](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@dwexler](https://community.sonarsource.com/u/dwexler)\
**Post date:** [March 27, 2024, 7:17pm UTC](https://community.sonarsource.com/t/pull-request-failure/112201/1 "2024-03-27T19:17:53Z")

</div>

Template for a good new topic, formatted with [Markdown](https://commonmark.org/help/):

- ALM used: Azure DevOps

- CI system used: Azure DevOps

- Scanner command used when applicable (private details masked)

- Languages of the repository: C#

- Private SonarCloud project

- Error observed (wrap logs/code around with triple quotes ``` for proper formatting)  
‘’’  
Caused by: Could not find the pullrequest with key ‘32359’  
Caused by: org.sonarqube.ws.client.HttpException: Error 404 on [https://sonarcloud.io/api/alm\_integration/show\_pullrequest?project=xxx&pullrequestKey=32359](https://sonarcloud.io/api/alm_integration/show_pullrequest?project=xxx&pullrequestKey=32359) : {“errors”:[{“msg”:“Unable to find the pullrequest with key \u002732359\u0027”}]}  
‘’’

- Steps to reproduce  
we fire off our PR’s through Azure DevOps CI/CD pipeline - no changes were made and it started failing at 3pm EST on 3/26

- Potential workaround  
None that we know of

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [March 28, 2024, 2:18pm UTC](https://community.sonarsource.com/t/pull-request-failure/112201/2 "2024-03-28T14:18:28Z")

</div>

Hey there.

Have you checked to see if the token set at the Organization level is still valid? (global **Administration \> Organization settings** )

You can also check if you have something configured at the project-level: (Project-level **Administration \> Pull Requests \> Integration with Azure DevOps Services \> Personal access token** ).

Typically when main branch analysis works but PR analysis fails, this is the culprit.

---

<div class="post-metadata">

**Author:** ![dwexler](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@dwexler](https://community.sonarsource.com/u/dwexler)\
**Post date:** [April 3, 2024, 5:15pm UTC](https://community.sonarsource.com/t/pull-request-failure/112201/3 "2024-04-03T17:15:30Z")

</div>

Yes, we not only verified the organization level token validity, but also tried running with a PAT on just the one project to no avail.

The error message is attached

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/c/f/cfea3aa1cf1f2e406e7d42bfb10a6b925806c035.png)

---

<div class="post-metadata">

**Author:** ![dwexler](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@dwexler](https://community.sonarsource.com/u/dwexler)\
**Post date:** [April 4, 2024, 1:08pm UTC](https://community.sonarsource.com/t/pull-request-failure/112201/4 "2024-04-04T13:08:18Z")

</div>

we found the problem based on this - thanks for the help