The sub-workflow you’re trying to execute limits which workflows it can be called by. Update sub-workflow settings to allow other workflows to call it.
in selfhosted Version 2.12.3 i have somehow lost ability to allow subflows for execution
was there at some point but now gone
@Edmunds_Priede You mentioned the setting existed before but is now gone. This could be because you were previously on a different n8n version or you were testing with a trial license that has since expired probably.
Does this help?
I don’t think this was removed, it’s still in the docs. What likely changed is feature availability.
The “This workflow can be called by” setting depends on workflow sharing and permissions, which aren’t fully available in Community self hosted. That would explain why you no longer see it.
If both workflows are yours, sub workflows should still work, just make sure you’re using the Execute Sub-workflow Trigger.
afaik the only workaround in community edition is just making sure both workflows are yours and using the execute sub-workflow trigger directly. theres no permission layer so if the workflows are in the same workspace, it should work fine. if youre trying to restrict which workflows can call which, unfortunately you need the paid version for that.