Making action webhook debugging easy
See original GitHub issueCurrently there isn’t enough information logged to figure out what went wrong with an action’s handler. We’ll need to capture the raw http request and response (headers + body) in our internal error’s detail, so that they are logged and sent to the client when requested with admin credentials. Maybe something like this along with our current error message?
{
"request": {"headers": {}, "body": ".."},
"response": {"headers": {}, "body": ".." }
}
We’ll need to be a little careful about logging headers which are derived from environment variables.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Complete Guide to Troubleshooting and Debugging Webhooks
Just like any debugging process, debugging webhooks starts with tracing the error source, reading any error messages, and interpreting the messages in order...
Read more >How to Debug Communications Webhooks - Easy-To-Use Tools
Use our simple tools to debug your Fax, Voice, and Messaging communications by analyzing webhooks. Watch a live demo today!
Read more >Webhooks for Beginners - Full Course - YouTube
What are webhooks ? Webhooks allow different web applications and services to communicate with each other. In this course for beginners, ...
Read more >Webhooks | Conversational Actions - Google Developers
The following sections describe common tasks that you can carry out in your webhook handlers. Send prompts. You can create prompts with simple...
Read more >Debugging remote webhooks with ngrok and Visual Studio
This method is accessible via HTTP POST, reads the input stream as a string, then returns a simple JSON success message. Add a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@0x777 this is not working as expected in Hasura Cloud. Even with environmental variable HASURA_GRAPHQL_DEV_MODE set as true. Cloud does not returns internal error for non admin roles. We use triggers for some unique validations and we are not able to show these validation outputs to users.
I did not address the actual issue in my above comment. When executing an action field, if we have to return an internal error because of the response from the handler, we will need to include the
request
andresponse
bodies of the actual call made to the handler in ourinternal
object.