5 months ago
We have N8N on our own servers and wanted to give Railway a go since our executions on our own servers are failing.
Now our first attempt failed according to the Deploy Logs of the primary. But in N8N itself the workflow is still executing but it is not proceeding anymore.
What is the problem here? Should we talk to sales for an enterprise solution? Would be great if we can get your help, thanks.
6 Replies
5 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
5 months 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 • 5 months ago
5 months ago
Hello! Can you please share the error logs if you dont mind? 
5 months ago
Hi, thanks for thinking along. That's one of the strange things, there is no error log. In the UI it states that it is canceled (look at execution 7, 8, 8 in the screenshot). But in the Deploy Logs of the primary it states that they were successful. But there was no output so they did not succeed.
Attachments
Hi, thanks for thinking along. That's one of the strange things, there is no error log. In the UI it states that it is canceled (look at execution 7, 8, 8 in the screenshot). But in the Deploy Logs of the primary it states that they were successful. But there was no output so they did not succeed.
5 months ago
Are you able to provide any more info on the type of thing being executed?
Is there any chance that the executions time out or have a failure?
Not an N8N pro myself but curious about eliminating the obvious.
5 months ago
Looking at your logs, it does look like there is an error...
Could you maybe show fully, or the start at least, as to what it is?
5 months ago
Just saw you also mentioned that the deployment on your own server is failing - is the version hosted on Railway a copy of that, with a restored database? Or is it a fresh environment?
If you had ported everything over from your server because you were getting an error and are still getting a similar error, it's most likely involving the configuration of the project or unlikely internally workflow related.
Like error had mentioned though, try to copy and paste that entire error and any other log that could possible help and we'll see if we can get anything out of that alone first off.