This topic was automatically generated from Slack. You can find the original thread here.
claire froelich : Love this tool!
Is there a way to view detailed error logs? I keep getting 422 for a github pull request workflow and am having trouble debugging
Dylan Sather (Pipedream) : welcome !
There should be some error observability displayed in the workflow, under the step that errored, but depending on the HTTP client that step is configured to use, it might squelch some important error data.
I can take a look if you’d like. Would you mind sharing your workflow with dylan@pipedream.com?
claire froelich : Hey Dylan! Thank you
As you can see there are plenty of errors to chose from 
Dylan Sather (Pipedream) : thanks! Do you see the Share button near the top of your workflow? You’ll actually need to add dylan@pipedream.com as a collaborator in order for me to see your event data, if that’s OK
claire froelich : Thanks, I’ve added you
Dylan Sather (Pipedream) : Take a look at the most recent event, I just modified the code a bit and replayed the prior event
claire froelich : wow how’d you do that!
claire froelich : was it this?
require("@pipedreamhq/platform") before the axios?
Dylan Sather (Pipedream) : This step was using the axios HTTP client by default, which doesn’t return the actual error data in a way that we can easily parse. We package our own version of axios (require("@pipedreamhq/platform").axios), which simply wraps axios and formats the data better
claire froelich : oh wow
Dylan Sather (Pipedream) : we need to go back and replace this in all of these pre-built actions!
claire froelich : it would be awesome if the templates used the pipedream hq axios by default, this is great
claire froelich : yeah!
claire froelich : anyway thanks a bunch i know how to fix it now 
Dylan Sather (Pipedream) : great!
