I’m deploying a Node.js/Express backend to Railway. The service starts fine, passes /api/health, connects to Postgres, and initializes Socket.IO. Right after the health check succeeds, Railway stops the container and npm logs npm error signal SIGTERM / command sh -c node dist/app.js. I already implemented graceful shutdown handlers (clearing intervals, closing Socket.IO, DB, etc.), so the signal itself isn’t fatal—it’s Railway sending SIGTERM. I’m trying to figure out why Railway is terminating the container right away.