<!--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=19954) </details> <!--IssueSummary end--> ### Summary CI pipeline stages appear to execute out of order. ### Steps to reproduce Make a pipeline with several stages and execute it. Honestly this was working fine for me until recently so I'm not sure what triggered it. ### Example Project My project which has this issue is https://gitlab.com/Queuecumber/linux-acs-override Take a look at the stage order in this pipeline: https://gitlab.com/Queuecumber/linux-acs-override/pipelines/13231453 Compared to the stage order as defined in my yaml https://gitlab.com/Queuecumber/linux-acs-override/blob/master/.gitlab-ci.yml ### What is the current *bug* behavior? When the job is queued, the stage order appears as defined in the CI yaml, when all the jobs are finished, they are shown in the wrong order and the results seem to match the incorrect order. ### What is the expected *correct* behavior? Pipeline executes in correct order ### Relevant logs and/or screenshots During pipeline execution:  After pipeline execution:  ### Output of checks This bug happens on GitLab.com #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)