Railway sent a signal to stop, and the worker shut down
proyectos2025ia
PROOP

a year ago

A few days ago, Railway sent a signal to stop, and the worker shut down cleanly. I don't understand why this happened if there were no errors in the processes or wait times.

I'd like to know what I can do to make this flow more robust, given that I don't have much experience with Railways.

Attachments

Solved

3 Replies

Railway
BOT

a year 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!


proyectos2025ia
PROOP

a year ago

it doesnt have de information for my problem


The SIGTERM didn't come from Railway, your deployed version of N8N sent that signal out to you. That is an issue you need to resolve with N8N.


Status changed to Awaiting User Response Railway 11 months ago


Railway
BOT

10 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 11 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...