Finding workflow run configuration

[EricTonissen]

I start a workflow with --project eridani

This workflow starts, and within this workflow I use another workflow.

The run_configuration was 'local' but changed it in every workflow and pipeline to eridani.

<run_configuration>eridani</run_configuration>

Why I got this error?

Where is it looking for the workflow run configuration?

I would expect that If the parent workflow can find it, that the child workflow also can find it.

2025/12/04 15:17:56 - tr_zorgoporde_extractie_based_on_itsm - Execution finished on a local pipeline engine with run configuration 'eridani'
2025/12/04 15:17:56 - jb_zorgoporde_extractie - Finished action [select extractie] (result=[true])
2025/12/04 15:17:56 - jb_zorgoporde_extractie - Starting action [execute extractie]
2025/12/04 15:17:56 - jb_zorgoporde_extractie - exec(5, 0, execute extractie)
2025/12/04 15:17:56 - execute extractie - Starting action
2025/12/04 15:17:56 - execute extractie - Loading workflow from XML file : [/opt/hop/eridani-base/pdi-repo/zorgoporde_extractors/jb_execute_extractie.hwf]
2025/12/04 15:17:56 - execute extractie - ERROR: Error running action 'workflow' :
2025/12/04 15:17:56 - execute extractie - ERROR: org.apache.hop.core.exception.HopException:
2025/12/04 15:17:56 - execute extractie - You need to specify a workflow run configuration to execute this workflow
2025/12/04 15:17:56 - execute extractie -
2025/12/04 15:17:56 - execute extractie - at org.apache.hop.workflow.engine.WorkflowEngineFactory.createWorkflowEngine(WorkflowEngineFactory.java:43)
2025/12/04 15:17:56 - execute extractie - at org.apache.hop.workflow.actions.workflow.ActionWorkflow.execute(ActionWorkflow.java:450)

[anntnzrb]

Run configuration must be set in the workflow action, not just child workflow XML. In ActionWorkflow.java, it reads from action config, not the child's XML. Open parent workflow → double-click the action → set "Run configuration" to "eridani" there.

[EricTonissen]

I figured out the reason why it didn't work. Within Pentaho you put in the name of the job or transformation without the extension. Within HOP it also needs the extension. Because we used a parameter for the job/transformation name (without the extension), HOP couldn't find this workflow/pipeline. The ERROR message is very confusing.