Customization Profiles visible via Execution Context API, but not applied by KNIME Executor

Hi all,

we have encountered an issue with Customization Profiles and the KNIME Executor.

When we apply the profiles through the Customization Profile workflow, everything appears to complete successfully. However, when we execute the workflows, the Executor continues to use the default profiles instead of the profiles we configured.

We noticed an additional detail that might help investigate the issue: when querying the Execution Context API, the customization-profile is correctly visible and contains the ID of the profile we configured. So, from the Execution Context side, the expected customization profile appears to be correctly associated.

Despite this, the Executor does not seem to use that profile when actually executing the workflow.

Our current KNIME Hub environment has:

• KOTS: 1.125.2

• KNIME Hub: 1.18.6

• Knime Analytics Platform: 5.8.2

Interestingly, we successfully performed the same configuration on another KNIME Hub environment with:

• KOTS: 1.121.0

• KNIME Hub: 1.17.1

Has anyone experienced a similar issue, particularly where the customization-profile is correctly returned by the Execution Context API but the Executor still uses the default profile?

Any suggestions or troubleshooting steps would be greatly appreciated.

Thank you!