Unable to see output of a compose action in run history
We're trying to debug a flow that had a null value submitted somewhere it shouldn't have.
One of the actions we have wont expand when clicked on. In previous runs of the same flow, this action expands just fine and shows the output.
The reason we are trying to debug this particular flow is that an unexpected null got into our inputs, and then an apply to each block tried to process it.
I think this would be one for Microsoft support since it'd be a bug in the UX but we dont have our Premier Power Automate Plan and Support yet (currently in the process of renewing our enterprise license for which we'll add it in)
If anyone here has the capacity to engage MS, or a way I can pass on the environment, flow and run id so they can take a look, that would be appreciated.
The only other way I could suggest to reproduce this is to take an array of strings from a previous action body that has a null in it. Create a compose action with the expression union(body('previous_action'),body('previous_action')) and see if the run history of that action has the null in it.