Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #214323
Closed (promoted) (promoted)
Open
Issue created Apr 14, 2020 by Andrew Newdigate@andrewnDeveloper

Merge request widget "could not retrieve pipeline status" error should be operationally observable

Sometimes the merge request widget will return a response like this:

image

Could not retrieve pipeline status. For troubleshooting steps, read the documentation.

When this happens, it seems that although this is a user-impacting error, it is not visible from an operational perspective:

  1. All HTTP calls association with the polling request returned successful HTTP error codes
  2. As far as I know, no log messages or sentry exceptions are logged when this error is generated

Since this has an impact on user-experience, we should, as operators of GitLab.com be able to determine when this is happening and (if possible) why.

At present I don't think this is possible.

Slack thread: https://gitlab.slack.com/archives/C101F3796/p1586860799050700 (while it lasts)

Another Slack thread: https://gitlab.slack.com/archives/C0SFP840G/p1590158858098700

Edited May 22, 2020 by Fabio Pitino
Assignee
Assign to
Time tracking