<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=29509) </details> <!--IssueSummary end--> ### Summary After pipeline succeeds, "Could not retrieve the pipeline status. For troubleshooting steps, read the documentation." appears. Very similar as this issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/41545 ### Steps to reproduce - Open MR - Trigger pipeline (which runs on external CI) that ends successfully *pushing code changes in the same MR branch* - Issue appears ### Example Project This is the pipeline triggered: ``` build: dependencies: [] stage: deploy before_script: - git config --global user.name ###### - git config --global user.email ###### script: - bundle exec fastlane ios dev_testflight - git push https://#username#:#token#@gitlab.com/#path#.git HEAD:"$CI_COMMIT_REF_NAME" tags: - ios only: - merge_requests except: variables: - $CI_COMMIT_MESSAGE =~ /Version Bump by fastlane/ ``` ### What is the current *bug* behavior? After the pipeline succeeds, the message appears and the protected branch MR cannot be merged. ### What is the expected *correct* behavior? After the pipeline succeeds, the MR can be merged without any trouble.