-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Triggers in manual mode hang if event is never emitted #6810
Comments
Hey @dlerman2, That is a good find, It looks like the stop button on the left has no impact. If you press the other stop button on the main workflow all is good. I suspect this will be an issue on all of the nodes I added that panel to a few weeks ago, I have created |
Thanks @Joffcom! FYI, for me, it doesn't seem to be tied to the left panel -- if I hit the stop button on the main workflow editor next to "Start Workflow", it hangs with a spinner, and I shut down N8N with ctrl-C, it hangs waiting for the workflow to end. |
Hey @dlerman2, That is interesting for me stopping it the other way wored as expected for the nodes I tested with but I am sure we will check this again while fixing it :) |
Encountered this issue on both RabbitMQ and Kafka Triggers. "Stop Listening" button has no apparent effect. Repeated attempts to click "Stop Execution" eventually hangs portions (e.g. Workflow List) of the UI too. The only way to get things working normally again seemed to be restarting the container.
top -H output within container (after clicking "stop execution" several times and UI side effects started)
|
Describe the bug
For triggers that implement
trigger(this: ITriggerFunctions)
, when you run them in manual mode (eg for testing while building a workflow), they normally run until a single event is emitted and then stop. If you instead click "Stop Listening" in the UI, the app hangs waiting for the single event to come, when instead it should probably callcloseFunction()
and exit.To Reproduce
Local File Trigger
Changes to a specific file
and enter any file pathListen for Event
Stop Listening
Expected behavior
I expect the trigger to stop listening and go back to edit mode.
Environment (please complete the following information):
own
,main
andqueue
. Default ismain
]: mainAdditional context
This seems to be true across multiple Triggers - I just used Local File Trigger because it's easy to test with.
The text was updated successfully, but these errors were encountered: