Sub-workflow names not shown in Hub execution logs when triggered from a main workflow

[DanielHua]

Hi everyone,

In our workflow setup, a main workflow (e.g., CCC_MAIN_PIPE) uses Workflow Reader + Workflow Executor to trigger multiple sub-workflows (e.g., CCC_RAW_DATA_MAIN_PIPE, CCC_REPORT_MAIN_PIPE, etc.).

When executed on KNIME Hub, we noticed that the execution logs only display the main workflow name (CCC_MAIN_PIPE), and do not show which specific sub-workflow is currently being executed.

This makes it difficult to track or debug the execution process, since all jobs appear under the same name in the Hub logs.

I’d like to ask:

1. Is there a way to make the Hub execution logs display the sub-workflow names?
2. Could this be achieved via flow variables, Logger nodes, or component encapsulation?
3. Are there any plans to improve sub-workflow traceability in future KNIME releases?

Thank you!

[mwiegand]

Hi @DanielHua,

whilst not tested when running on the Hub, give the following Java code a try to trigger logs:

logWarn(
	"\n\n/********************\n/***** New Section *****\n/********************\n" +
	"Domain: " + v_Domain + "\n" +
	"Start: " + v_Start + " // End: " + v_End + "\n" +
	"Section: " + v_SectionID + "\n" +
	"Result Count: " + v_ResultCount + "\n\n\n"
	);

I use it during execution of highly complex workflows, iterating in parallel over complex scenarios.

Best, Mike
CTO @ DataNautics GmbH - Your KNIME-Experts
Contact: info@datanautics.net // datanautics.net // +49(0)170-325 713 9 // Linkedin
Daten Automatisierung für Finanz-, Produktion-, IT- und Marketing-Prozesse mit KNIME

[DanielHua]

@mwiegand

use it during execution of highly complex workflows, iterating in parallel over complex scenarios.

Best, Mike
CTO @ DataNautics GmbH - Your KNIME-Experts
Contact: info@datanautics.net // datanautics.net // +49(0)170-325 713 9 // Linkedin
Daten Automatisierung für Finanz-, Produktion-, IT- und Marketing-Prozesse mit KNIME

Hi Mike,

Thank you for your suggestion, and I really appreciate you sharing the Java snippet.

I have tested a simplified version of logWarn inside a component, and the logs do appear in the Hub job output. This does make the execution process a bit clearer.

I will try adding more detailed logWarn messages inside each sub-workflow as you suggested to improve traceability.

If you or the KNIME team plan to enhance sub-workflow visibility in Hub execution tracking in the future, that would be very helpful for complex enterprise workflows.

Thanks again for your support.

Daniel

[mwiegand]

You are most welcome. If you don’t mind, would you be so kind to mark my prev. reply containing the Java code as the solution please?

[DanielHua]

Thank you for your support. I have now marked your earlier reply containing the Java code as the accepted solution. I appreciate your assistance!