'Run Pipeline' button loading spinner that never finishes
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
In the Merge Request Pipelines tab, clicking Run pipeline sometimes results in a loading spinner that never finishes and the pipeline is not triggered. For some users it completes after ~10 seconds, but for others it keeps spinning for over a minute with no pipeline created and no UI error.
Steps to reproduce
- Open any open Merge Request.
- Go to the Pipelines tab.
- Click Run pipeline.
- Observe the button spinner and whether a pipeline is actually created.
Example Project
I cannot share a public/open-source example project or MR that reproduces this (private/internal projects only).
However, I attached a screen recording that includes the full UI behavior and the browser Network tab (including requests triggered by clicking Run pipeline).
What is the current bug behavior?
After clicking Run pipeline, the UI shows a loading spinner on the button and does not complete.
- Some users: pipeline starts after ~10 seconds.
- Other users: spinner continues for 60+ seconds and no pipeline is created (no visible error message in the UI).
What is the expected correct behavior?
Clicking Run pipeline should reliably trigger a pipeline and update the UI accordingly. If the request fails or times out, the UI should show a clear error message instead of spinning indefinitely.
Relevant logs and/or screenshots
I will attach:
- Screen recording showing the stuck spinner and the Network tab requests/responses when clicking Run pipeline.
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
GitLab Enterprise Edition 18.8.0-pre (b60708acf8b) - cloud version
Results of GitLab application Check
Expand for output related to the GitLab application check
N/A (cloud instance)