Subworkflow Issue

[Tim_C]

Describe the problem/error/question

Unable to call sub workflows, we get an error about permissions. The KB says to set the permissions on the sub workflow, but we don’t have anything there to do that:

What is the error message (if any)?

ERROR: Target workflow ID may not be called

Please share your workflow

Share the output returned by the last node

n/a

Information on your n8n setup

• n8n version: 1.26.0
• Database (default: SQLite): Postgress
• n8n EXECUTIONS_PROCESS setting (default: own, main): Main
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Ubuntu

[Tim_C]

Update: Nevermind, I updated to 1.27.1 (instead of 1.26.0) and now they are working as expected

[Tim_C]

And it broke again, even more generic error now:

[MutedJam]

Hi @Tim_C, I am very sorry you are having trouble.

Can you confirm which version and which edition of n8n you are currently using? Keep in mind that most sharing-related functionality is only available on Pro and Enterprise Cloud plans, as well as Enterprise self-hosted plans. If you are using one of these plans but don’t see the field highlighted below, there might be a problem with reading your license information.

In addition, can you confirm the ownership of your workflows? Are sub-workflow and the current workflow owned by different users and if so, which roles do they have?

[Tim_C]

Hey there!

This is a self-hosted n8n without a paid license, so we only have 1 user/owner of all the workflows

Tim

[MutedJam]

Thanks for confirming @Tim_C! Can you check the owner situation directly in your n8n instance database? If you look at the shared_workflow table, do both your “parent” workflow and the sub-workflow have the same workflow:owner?

And is this user the user you are currently logged in as?

[Gowthaman_Prabhu]

@MutedJam V 1.28 unable to call a sub workflow owned by another user.

Both the users (current WF and sub WF) are of role global:owner.

Is this an intended restriction?

[BramKn]

Hi @Gowthaman_Prabhu

Yes this is intended, as n8n does not allow for multiple owner users.