[JENKINS-63820] No flow execution for input in lock block after restart

After restart, having input step inside lock and several jobs waiting to acquire the lock, not able to Proceed or Abort anymore.

Steps to reproduce:

1) Have "input" inside a lock block

2) Start several build of the same job (the earliest will block on "input" and others block on "lock")

3) Restart Jenkins

Observed behaviour:

Can not Proceed or Abort the build with buttons anymore. Even generic abort button does not work for the build, have to "kill" it.

Expected behaviour:

One can Proceed or Abort the build.

Minimal pipeline to reproduce:

```
pipeline {
agent none
stages {
stage('a') {
steps {
lock('lock-me-in') {
script {
input 'Are you okay?'
}
}
}
}
}
}

```

Output in the jenkins log:

```
WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction: no flow execution found for input-simple #8

```

---
Originally reported by ysoldak, imported from: No flow execution for input in lock block after restart

• status: Open
  
• priority: Minor
  
• component(s): lockable-resources-plugin, pipeline-input-step-plugin
  
• resolution: Unresolved
  
• votes: 3
  
• watchers: 6
  
• imported: 20251217-081411
  

Raw content of original issue

After restart, having input step inside lock and several jobs waiting to acquire the lock, not able to Proceed or Abort anymore.


Steps to reproduce:

 1) Have "input" inside a lock block

 2) Start several build of the same job (the earliest will block on "input" and others block on "lock")

 3) Restart Jenkins


Observed behaviour:

 Can not Proceed or Abort the build with buttons anymore. Even generic abort button does not work for the build, have to "kill" it.


Expected behaviour:

 One can Proceed or Abort the build.


Minimal pipeline to reproduce:



pipeline {

    agent none

    stages {

        stage('a') {

            steps {

                lock('lock-me-in') {

                    script {

                        input 'Are you okay?'

                    }

                }

            }

        }

    }

}





Output in the jenkins log:



WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction:  no flow execution found for input-simple #8

environment

```
Jenkins: 2.259

Lockable resources plugin: 2.10

Pipeline Input Step: 2.12
```

Start with the minimal pipeline in the issue and reproduce the restart scenario using the lockable-resources-plugin and pipeline-input-step-plugin versions described. Inspect the Jenkins log warning about the missing flow execution, then verify that Proceed, Abort, and the generic build abort work after restart.

Written by the indexing model from the issue text.