n8n - 💡(How to fix) Fix "Go to Sub-workflow" shows "Workflow not found" when sub-workflow ID is set via expression {{ $workflow.id }} [1 comments, 2 participants]

When an Execute Sub-workflow node is configured by ID using the expression {{ $workflow.id }} (to dynamically reference the current workflow), right-clicking the node and selecting Go to Sub-workflow opens a new tab and shows a "Workflow not found" error screen. This is unexpected - the workflow ID is valid but the URL does not resolve it correctly (.../workflow/=%7B%7B%20$workflow.id%20%7D%7D) which leads to a redirect to .../entity-not-found/workflow and the error screen. It should not show a "Workflow not found" error.

TL;DR

The issue can be resolved by properly encoding the workflow ID expression {{ $workflow.id }} in the Execute Sub-workflow node.

Guidance

• Verify that the workflow ID expression {{ $workflow.id }} is correctly resolved at runtime by checking the node's configuration and the workflow's context.
• Check if there are any existing issues or limitations in n8n version 2.19.0 related to dynamic workflow ID resolution.
• Consider using a hardcoded workflow ID as a temporary workaround to confirm if the issue is specific to the dynamic expression.
• Investigate if there are any URL encoding issues that might be causing the .../workflow/=%7B%7B%20$workflow.id%20%7D%7D redirect.

Example

No code snippet is provided as the issue seems to be related to the n8n workflow configuration and expression resolution.

Notes

The issue might be specific to the n8n version 2.19.0 and the Linux operating system. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Use a hardcoded workflow ID as a temporary solution until the dynamic expression resolution issue is resolved. This is because the hardcoded workflow ID works as expected, and using it can help confirm if the issue is specific to the dynamic expression.