It would be a real valuable addition when we can export the entire call tree of a (sub) microflow.
In complex projects, nesting goes quite deep and you end up with using the 'find usage' feature quite a lot. It would be so much better if you can export the entire tree or make it visual in one click how the entire tree is built up for the usage of a specific (sub) microflow.
It can be of course that one (sub) microflow is used in multiple microflows but then this should result in multiple call trees/maps.