Hey our containers are are stopping, this happened previously some months ago but started happening again, is there some way of accessing the logs for the container so we can have a better idea of whats going on ?
here are some of the logs we see bfore goes down https://railway.app/project/94efdbb0-a582-46db-b2de-079cbe08996f/logs
in case u cant see it

npm ERR! path /app

npm ERR! command failed

npm ERR! signal SIGTERM

npm ERR! command sh -c node dist/app.js

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-08-09T15_18_45_404Z-debug-0.log

npm WARN config production Use --omit=dev instead.

> ascend@1.0.0 start

> node dist/app.js

npm ERR! path /app

npm ERR! command failed

npm ERR! signal SIGTERM

npm ERR! command sh -c node dist/app.js

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-08-09T15_18_45_688Z-debug-0.log

npm WARN config production Use --omit=dev instead.

> ascend@1.0.0 start

> node dist/app.js

Server is running on port 8080

npm ERR! path /app

npm ERR! command failed

npm ERR! signal SIGTERM

npm ERR! command sh -c node dist/app.js

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-08-09T15_18_36_576Z-debug-0.log

npm WARN config production Use --omit=dev instead.

> ascend@1.0.0 start

> node dist/app.js

Server is running on port 8080

npm WARN config production Use --omit=dev instead.

> ascend@1.0.0 start

> node dist/app.js

Server is running on port 6185

npm WARN config production Use --omit=dev instead.

> ascend@1.0.0 start

> node dist/app.js

Server is running on port 7796

npm WARN config production Use --omit=dev instead.