18 days ago
I simply don't understand why my applications stopped running - even after upgrading. So when I click on the start workflow buttons, it just starts spinning non stop. I have checked with Google if they are blocking my app but they've said they've not blocked anything.
Besides, I'm still able to use the same API keys for the same workflow running on make.com.
What's wrong?
I even check the console log and no HTTP requests are even being logged.
Meaning, while the wheel is pinning, the app is not running at all.
4 Replies
18 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 18 days ago
18 days ago
That's... really weird, maybe ur using queue mode (EXECUTIONS_MODE=queue) but don’t have a worker running? If you don’t spin up a separate n8n worker, nothing runs, it just sits there spinning.
Could also be a DB issue, if your DB is messed up or n8n can't connect to it, workflows won't run but UI still loads. Try to verify this.
Just to make sure, you have the same versions running on both Railway and make.com, right?
18 days ago
This has happened to me twice.
The first time it happened it took two days. I thought I needed to give the server time to rest... but still didn't work. Then I launched a new install of n8n and it worked till now. The very same installation stopped working. Then I launched a different installation of n8n, imported the exact same workflow it work.
So my workflow starts with a form trigger that asks for the spreadsheet ID where I have provided a list of rows to iterate through. When I click on Test Workflow, the forma is launched and I provide the spreadsheet ID, and submit. The Test Workflow then starts spinning forever. I check the form trigger and it says waiting for form to be submit. But I already submitted the form.
It is happy to take a whole day waiting for this form to be submitted while spinning itself.
What could be wrong?
It's been working.
This has happened to me twice.The first time it happened it took two days. I thought I needed to give the server time to rest... but still didn't work. Then I launched a new install of n8n and it worked till now. The very same installation stopped working. Then I launched a different installation of n8n, imported the exact same workflow it work.So my workflow starts with a form trigger that asks for the spreadsheet ID where I have provided a list of rows to iterate through. When I click on Test Workflow, the forma is launched and I provide the spreadsheet ID, and submit. The Test Workflow then starts spinning forever. I check the form trigger and it says waiting for form to be submit. But I already submitted the form.It is happy to take a whole day waiting for this form to be submitted while spinning itself.What could be wrong?It's been working.
18 days ago
Hmm... maybe your Form Trigger's webhook isn’t properly reaching your n8n instance, which is often due to misconfigured N8N_HOST, WEBHOOK_URL, or protocol settings. This causes the workflow to wait forever for a submission that never arrives. But also, (again) if you use queue mode (EXECUTIONS_MODE=queue) but don't have a running worker or Redis is down, workflows will stall, and it could also be a problem with the DB's content or connection.
You gave me more information without telling me if you took in mind what I said or answered my question, I would be glad if you did :D
Anyways, the new advice I can give is to please check your webhook URL manually, and afterwards make sure the related environment variables (N8N_HOST, N8N_PROTOCOL, WEBHOOK_URL) are correctly set.
(Also restart your n8n service to clear stuck executions)
lofimit
Hmm... maybe your Form Trigger's webhook isn’t properly reaching your n8n instance, which is often due to misconfigured N8N_HOST, WEBHOOK_URL, or protocol settings. This causes the workflow to wait forever for a submission that never arrives. But also, (again) if you use queue mode (EXECUTIONS_MODE=queue) but don't have a running worker or Redis is down, workflows will stall, and it could also be a problem with the DB's content or connection.You gave me more information without telling me if you took in mind what I said or answered my question, I would be glad if you did :DAnyways, the new advice I can give is to please check your webhook URL manually, and afterwards make sure the related environment variables (N8N_HOST, N8N_PROTOCOL, WEBHOOK_URL) are correctly set.(Also restart your n8n service to clear stuck executions)
17 days ago
I have checked the executions mode and I see it's correctly set as you said https://snipboard.io/FJP53t.jpg
Once more thing; this kind of thing usually only happens when I change from Railways assigned domain to my own custom domain. Initially the installation I am now using had the same thing. I switched to my own custom domain then it just broke. Then I had to install a new n8n instance here on Railways. After once month I updated the custom domain again like three days ago so that I can work from my own domain and now I am having the same problem.
Interestingly, the previous installation that failed to work, now works - and I didn't do anything.
"Form Trigger's webhook isn’t properly reaching your n8n instance, which is often due to misconfigured N8N_HOST, WEBHOOK_URL, or protocol settings."
-this could make some sense. but how do I restart the n8n instance. I'll Googled around but all options assuming I am working with a cmd. But I don't use cmd!
-I dug deeper into the logs and found something like this https://snipboard.io/PpUMRm.jpg Can you make sense of this?