The last message 19 days ago in topic (Problem running workflow: Connect a trigger to run this node - #11 by zakiki) was:
‘The engineers of n8n will be working on this next week, it is confirmed by n8n to be a bug.’
Today I checked version 1.87.0, this bug is not fixed.
There is a task in GitHub, but probably no one paid attention to it.
But this error greatly interferes with debugging processes.
How can we influence the n8n team to pay attention to this problem?
Hi @korovaevda
Sometimes it can take a bit of time as they are very busy. But if it is on GitHub it will get picked up at some point.
As far as I know the person telling you that is not part of n8n, so not sure where they got their information.
As far as I can see it is not really a high priority bug to solve, as it does not break any workflows and there is easy workarounds. So probably is gonna be a while if it is not an easy fix.
I get this even when I have a trigger, if any of my nodes are pinned. Actually I can’t reproduce this now. But when it happens, the only workaround I know is to exit and reenter the workflow.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.