Forum Discussion
To my knowledge only way is to create a trigger task for invoking the pipeline and Call it with required Pipeline parameters
The problem with changing pipeline parameters during an execution is that it makes it really easy to introduce unpredictable results. For example, if Snap A references a parameter that is changed by Snap B, the value of the parameter read by A would be completely unpredictable since all of the Snaps are running in parallel. In other words, the value of the parameter read by Snap A might be “foo” for the first 20 docs in one run and then “bar” after that. But, if the pipeline was run again with the same inputs, the parameter might be “foo” for the first 10 docs instead of the first 20. So, to avoid these race conditions, parameters are treated as static.
If you need to change a parameter for a subsection of a pipeline, you can move that subsection into a child pipeline and call it with Pipeline Execute, setting the parameters as needed.
Are you calling the task from another pipeline in this case? Is there a reason the Pipeline Execute snap does not work for you?