With Muse behaviour, I’m struggling to debug something that is going wrong within a subgraph that is being run from my main graph. All I can see is that the subgraph node is failing. I wish there was a was to ‘step into’ the subgraph when debugging, or to expand it within the main graph, or even if I just had to open the subgraph and could still debug what is going on in there (but opening the subgraph doesn’t let me select an object for an agent running the supergraph). Maybe I’m missing some way to achieve this? Or maybe support for one of these options might be added in the future? I hope so!
1 Like
Hey @Andy-Block , are you on Discord? Can we try and screenshare to look at the issue to make sure we understand it correctly? 
Thanks!
Hi @ShaneeNishry,
Sorry for the delayed response… I am on Discord, but I’m on holiday for a few days. I’ll be back on Monday - maybe we can find a time after that… I’m not sure what timezone you are in though? I’m in CET.
In the meantime, I’ll briefly try and explain a bit more what I mean… if you have a behaviour tree with a “Run subgraph” node, I don’t see any way you can use the ‘Debug’ button to debug what is going on inside the subgraph. You can see that the subgraph as a whole has succeeded or failed (based on the status shown for the ‘Run subgraph’ node), but can’t see where it failed or which nodes were executed. If there is a way to do that, I’d be interested to know how!
Kind regards,
Andy
Hey Andy, no worries, we’ll test if it’s still broken for our new release and see if we can squeeze a fix in time, if not it’ll come soon after the release!
I’m on BST / UK time
1 Like