(How) can I remove incomplete deployments from environment view?

I have multiple environments that are being deployed from my pipeline. The pipeline needs a successful build step and deploy step to deploy to an environment. The deploy step is activated manually.
When I click on Operate > Environments, I can look up which branch was last deployed on each environment.
However, under my environment “production”, I not only see the last successfully deployed branch, but a stopped one as well. This is marked as “waiting”, because after the successful build step I never manually started the deploy step for this pipeline (the build step was a test and I cannot run the deploy step without breaking production).

Now it seems I am forever stuck with this old incomplete pipeline in my environments view. It is a cosmetic issue only, but quite irritating.
I even tried deleting the regarding pipeline, with no effect.

Is there a way to get rid of it or will it stay as log as the environment exists?

I’m working on cloud GitLab Enterprise Edition 16.5.0.

Did you ever found an answer for your questions? We have the same probleme

No solution so far. The pipeline I see as “waiting” has since changed though. Maybe it shows only the latest pipeline that’s in waiting status (in addition to the latest successful one).

I think the “short” Environment view shows the latest successful and the “upcoming” job. When deploying to an environment, that job will be the “Running” one currently targeting the environment.

The fact that “Waiting” jobs are included in the list makes the long-list of environment’s jobs pretty useless though. If I wanted to see what were the last 3 deployments into my environment, I’d have to go through potentially many pages of the jobs list - since there is no way to filter out only the jobs that were actually executed.

Waiting jobs should be excluded by default, or at least there should be the option to do so in the view.