After upgrading to 0.201.0, the http node no longer returns the response headers from the QuickBooks Online API. Not sure if it’s affecting other APIs as well. I verified the issue by downgrading to 0.200.1.
This makes it impossible to troubleshoot issues with my API queries since I can’t get the details of what’s wrong with my request.
Hey Jon, that is the issue - 0.200.1 shows me the details I need, but in 0.201.0, those details don’t show up (the two screenshots show the difference in output).
EDIT: Also when i expand details, there is nothing useful in there (same behaviour the previous version shows the correct error response from the QBO API)
Sorry I meant if you click on the Details text at the bottom you sometimes get more information. When I am using the HTTP Request node though I tend to prefer checking the Never error box as well which then outputs the data so I can manually check the status code and get more meaningful output.
I suppose I will use that to troubleshoot, but it’s interesting how it n8n no longer picks it up from the standard error response (also, it’s not the best solution because the workflow should fail if there is an error in the response)
What I tend to do is after an HTTP Request node check the status code if it isn’t a 200 or another “success” code I use a stop and error node so I get the same thing with the workflow stopping but I have a lot more control over the error.
