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

KNIME Analytics Platform
1

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!

2

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"
	);

image
image1044×957 38.1 KB

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

2 Likes