Hi!
Weird. I was able to see that behavior (on Rundeck 4.10.2) but after touching “required”/“restriction” parameters (and save it) it works as expected (your goal) . Could you try with the following job definition?
- defaultTab: nodes description: '' executionEnabled: true id: eac8952d-347d-4400-bc2f-945c7884267a loglevel: INFO name: Hiya nodeFilterEditable: false options: - delimiter: ',' multivalued: true name: user value: 'bob,charlie' values: - alice - bob - charlie valuesListDelimiter: ',' plugins: ExecutionLifecycle: null scheduleEnabled: true sequence: commands: - exec: echo ${option.user} keepgoing: false strategy: node-first uuid: eac8952d-347d-4400-bc2f-945c7884267aTry editing the job, change some parameters like “restriction”, save your job and try again.
This could be a strange bug related to options.
Also, could you share your example job definition to take a look?
Thanks!