The option fullResponse as described here is not working in the development environment. The error in the callback is still the shortened version.
How can I get the full response in a development environment, and will I have access to the full error message in production?
My use case is seeing the full error from a failed multi-call, so I can find the correct index to begin the retry from.