@FabulousFab Thanks!
I have run into the same issue before, whet I think happens is that when parsing the outputs, for some reason Power Automate forces the value as a string as you can see in you example
But in your "Respond to a PowerApp or flow" you are requesting integers. So, the error you are seeing is an error when the expected value should be an integer but received a string.
Is a silly fix but what I have done to fix this is to convert to integer, you can do it for just 1 output parameter result like this:
int(your_outputs)
then, trigger the flow from you app. If you look at the flow output again, that should unstuck whatever bug there is in the flow and show your values as integers now.
Once you get your outputs as integers, you can remove the int function and it should still work.
I am also assuming that your outputs are correct and only returning the integer value and nothing more. If you still have issues with this you could show your output expressions.
