Gitlab CI manage blocked stages as running stages

Hello :slight_smile:

I’m trying to create a automation process for my project in GitLab CI and I have some troubles understanding why the pipeline get blocked, then keep running after I launch It.

The first job is manual and I’m trying to link jobs using the ‘needs’ keyword. But no matter which ‘when’ clause I use, It’ll keep blocking the pipeline and set the ‘create’ state to all jobs. After I run a job of a blocked stages, the stage stay in the ‘Running’ state even after the job as ended.

I don’t expect the jobs to be set at the ‘created’ state since It should wait for the first job to be launched. And to be set as ‘skipped’ when jobs have been run. What am I missing?

Here’s the project :

Thanks for your answers!