Thanks for the details, I have validated the other two issues again and I seem to have found working solutions for both. The first issue from my original post seems to be fixed by using the onError method instead of catch, this seems like a bug considering the different results between node.js and a...