The issue here was anytime an exception occurred when the API was called, the catch block
was sending an Exception Object to the Write-VerboseLog, which didn't know how to handle that
and would treat it as a JSON object, which would put it into an infinite loop. The fix was
to ensure that we were sending in the $_.Exception.Message which is a string.
Fixes #268
The issue here was anytime an exception occurred when the API was called, the catch block was sending an Exception Object to the Write-VerboseLog, which didn't know how to handle that and would treat it as a JSON object, which would put it into an infinite loop. The fix was to ensure that we were sending in the $_.Exception.Message which is a string.