Called Workflow Failure from Unimportant Warnings

I am calling a second workflow to generate multiple BIRT reports. After a minor midstream change to the called “child” workflow, the Call Local Workflow node is now failing and only showing the same unimportant warnings that were present in the child workflow prior to my change. Any idea why all of a sudden the same warnings might cause the workflow to fail?

Failure, workflow was not executed.
Column Appender 5:3915: Table 1 is shorter than the longest table. Corresponding columns were filled using missing values.
Missing Value 5:3920: The current settings use missing value handling methods that cannot be represented in PMML 4.2
Column Appender 5:3923: Table 1 is shorter than the longest table. Corresponding columns were filled using missing values.
Column Appender 5:3929: Table 1 is shorter than the longest table. Corresponding columns were filled using missing values.
Missing Value 5:3932: The current settings use missing value handling methods that cannot be represented in PMML 4.2
Column Appender 5:3944: Table 1 is shorter than the longest table. Corresponding columns were filled using missing values.
Missing Value 5:3953: The current settings use missing value handling methods that cannot be represented in PMML 4.2
Column Appender 5:3964: Table 1 is shorter than the longest table. Corresponding columns were filled using missing values.
Missing Value 5:3969: The current settings use missing value handling methods that cannot be represented in PMML 4.2
Column Appender 5:3975: Table 1 is shorter than the longest table. Corresponding columns were filled using missing values.
Missing Value 5:4271: The current settings use missing value handling methods that cannot be represented in PMML 4.2
Column “Export (#1)” still contains missing values.
Column “Sum(Amount)” still contains missing values.
Missing Value 5:4280: The current settings use missing value handling methods that cannot be represented in PMML 4.2
Column “Export (#1)” still contains missing values.
Column “Sum(Amount)” still contains missing values.
Column Appender 5:4306: Table 1 is shorter than the longest table. Corresponding columns were filled using missing values.
Missing Value 5:4307: The current settings use missing value handling methods that cannot be represented in PMML 4.2
Missing Value 5:4311: The current settings use missing value handling methods that cannot be represented in PMML 4.2

I was able to solve it using my standard approach of going back to the original unaltered child workflow, altering it again and then saving it under a new name. I always only work in saved copies of a called workflow because of these weird quirks, but I would love to know what actually causes these failures as this kind of thing happens a lot.

Hello @iCFO,

I am happy to hear that you could resolve the issue by using a previous version. However, I understand that you would like to understand the root cause. May I ask if the called workflow is partially executed when the fails or is it not executed at all? In the latter scenario, I would wonder where the messages are coming from. Could you also share a screenshot of your workflow (or even an insensitive workflow example) of the failing setup?

Best regards,
Kevin

The called workflows are always fully reset before saving. Unfortunately I have already replaced the called workflow that threw the failure which cited the list of the above warnings. The called workflows throwing a failure always function fine when they are run directly as a standalone workflow using the same data. The “warnings” listed are always present in the called workflow, but they serve no purpose as those nodes are configured and operating as intended. It seems to me that this is another reason why users should have the ability to suppress node “warnings” that regularly occur with proper configuration.

I will try to remember to upload a trimmed down version with dummy data the next time it happens. Thanks for the reply!

Thank you for for bringing this up.
Would be very interesting to dive into your workflow example, once you remember.
In general, suppressing these warnings could be an improvement. But this wouldn’t change the failed status of your node though.