-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Respond to callback not working when using wait node option “On webhook call” #13633
Comments
Hey @brunolnetto, We have created an internal ticket to look into this which we will be tracking as "GHC-1029" |
are you running multiple main instances? |
A single main instance. I added a missing clause 'Wait For Sub-Workflow Completion' on the node 'Execute Workflow'. |
Hey @brunolnetto, What seems to be happening here is the Execute workflow is waiting for the sub workflow to complete before moving on which means the wait node isn't waiting for the URL to be hit so it isn't properly listening on the resume URL. If you update the Execute Workflow node and set I don't think this is a bug as I wouldn't expect the wait node to be waiting before it has started. |
Ops, too late. I updated the post with my further discovery, but you were faster than me. By responding immediately, it still does not work in production mode, only on test mode. |
Hey @brunolnetto, Ah yeah look like you are right, I suspect this will be linked to workflows hitting the database in a waiting state and "finishing" before the workflow has actually finished. I will pass this back to the team that looks after this area for further thought. |
Bug Description
Describe the problem/error/question
I try to perform an action where I trigger a workflow and wait it to callback the main execution back. It works, partially, and I am getting trouble to make the Webhook respond properly. When I set the main workflow to "Respond to Webhook", it does not respond to the FORMER HTTP Request. I am almost sure, the reason for the webhook not responding anymore is because I activate the "wait node" with option "On webhook call", a bug in my opinion: Even though I set it as "Respond immediately", other webhook calls just get "overlooked" or "overwritten" somehow...
I manage to design this minimal example below. For some unknown reason to me, it works in test mode, but not in production mode.
/
Please share your workflow
Information on your n8n setup
To Reproduce
curl
. Then perform a GET request on the workflow;Expected behavior
I expected to receive the result.
Operating System
Ubuntu Linux 20.04
n8n Version
1.80.5
Node.js Version
20.18.3
Database
PostgreSQL
Execution mode
queue
The text was updated successfully, but these errors were encountered: