Backend: JobPlay Input sending invalid value for id (bridge) when it is expecting build

Summary

Trigger jobs for Downstream pipeline jobs that are configured to run as manual fails to start using the main play button at the Build > Pipelines page. However this will succeed if you to the >> button and click on the individual trigger job.

Steps to reproduce

1. Create an upstream pipeline with the following .gitlab-ci.yml.

stages:          
  - build
  - test
  - deploy

dummy-build-job:
  stage: build
  variables:
    V1: "HELLO"
  script:
    - echo "this is a dummy build job"

trigger-job:   
  stage: test
  variables:
    V1: "HELLO"
  trigger:
    project: path/to/dowstream_pipeline
    branch: main
  when: manual

2. Create a downstream pipeline the following .gitlab-ci.yml.

stages:          
  - deploy

deploy-job:      
  stage: deploy  
  environment: development
  script:
    - echo "Deploying application..."
    - echo "Application successfully deployed."

3. Run the pipeline in the upstream pipeline.
4. Wait for the trigger-job to be created.
5. Click on the big Play button and see this error: Variable $id of type CiBuildID! was provided invalid value

6. Click on the small Play button on the trigger job directly and see the job succeed.

Example Project

• https://gitlab.com/kballon-bug-report/zd551409_upstream_pipeline
• https://gitlab.com/kballon-bug-report/zd551409_dowstream_pipeline

What is the current bug behavior?

• The trigger job succeeds when using the big Play button.
• The trigger job succeeds when using the small Play button.

What is the expected correct behavior?

• The trigger job fails to start when using the big Play button.
• The trigger job succeeds when using the small Play button.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

  (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\\\`)   

Results of GitLab application Check

Expand for output related to the GitLab application check

 (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)  

Possible fixes