Confusing button behavior for manual ci jobs.

Summary

There is a confusing button within a button interface. Going to the console page for a manual ci job should show a play button but it doesn't.

Steps to reproduce

Define a manual ci job, example below. See attached screen capture: gitlab-ci-manual-no-play-button

That brings you to:

Going back and clicking the little play button inside the job button actually gets it to run:

What is the current bug behavior?

Pressing the outer button takes you to the console screen and it seems like the job is running, but the job never starts. It actually has to be cancelled first, then it the retry button shows up on the console page.

What is the expected correct behavior?

Either the outer button should start the job, or a play button should appear on the page you are taken to.

Relevant logs and/or screenshots

Sample .gitlab-ci.yml file:

stages:
  - deploy

variables:
  PROJ_NAME: robin

docker_build_release_tag:
  stage: deploy
  only:
    - tags
  script:
    - IMAGE_NAME="larktech/$PROJ_NAME:$CI_COMMIT_REF_NAME"

    - docker build -t $IMAGE_NAME .
    - docker push $IMAGE_NAME

prod_deploy:
  stage: deploy
  when: manual
  only:
    - tags
  script:
    - IMAGE_NAME="larktech/$PROJ_NAME:$CI_COMMIT_REF_NAME"
    - kubectl --context k8s-prod.lark.com set image deployment/$PROJ_NAME-deployment $PROJ_NAME=$IMAGE_NAME

Output of checks

This bug happens on GitLab.com