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
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.