Whilst testing a simple workflow that has a Webhook that calls an HTTP request, often times when I test it using Postman, it will show it’s still waiting for a request to come in, but when I check the execution in another tab, it’s already done processing. This happens when the workflow completes with or without errors.
I’ve seen this before and manually rebuilding my workflow solve it before (or that may have been a coincidence), but this time the new workflow is still hanging.
So far it just seems to be an issue of testing the workflow.
Anyone know what might be causing this?
This means you’re not responding properly to your client, in this case Postman. Please share your workflow in a code block so we can see how you have implemented your webhooks. Below is an example which will always return a valid response. Also make sure that you have error handling. If your workflow errors out on a specific step, you might not be sending a response to the client which will eventually timeout:
The best practice in my opinion is to always use a respond to webhook node to hande your different responses instead of just allowing the workflow to respond with the last node’s ouput
Success:
Error:
Thanks for the reply. I may not have explained my problem correctly. What I meant was while debugging/testing my workflow, I send a request using Postman (the client does not matter), and n8n will continue to show “Listening for test event” even after it received the event, processed it successfully (or not), and sends a response back to Postman.
I try to lick the “Stop listening” button but it won’t stop. The debugger is hung. the only option I have is to refresh the page then I can see the execution happened just fine.
It seems more like a glitch as it doesn’t happen all the time. Do you know why this might be happening?
Thank you.
Oh yes this happens to me often as well. I simply make sure the workflow is saved and then refresh the page for it to start working again.
