My app (school-mgmt, project "disciplined-achievement") is failing to

start with "Application failed to respond" — has been down for over an

hour.

Deploy logs show only two lines and nothing further, even on completely

fresh containers (confirmed via different bind-mount volume IDs across

two separate attempts):

Mounting volume on: [path]

Starting Container

No further output appears — not even the app's own startup script

banner. This happens after both a plain restart and a full fresh

redeploy.

Already ruled out on my end:

• No active platform-wide incident on status.railway.com

• CPU and memory show no spike/usage at all during the stuck period (not

  an OOM kill)

• The attached volume shows healthy, stable usage (~33MB, flatlined, not

  full or growing)

• Only one deployment shows as Active — no stale/duplicate deployment

  conflict

• The Postgres database in the same project did restart once earlier

  (~08:37 UTC) after I toggled its Public Networking setting, but it

  recovered cleanly within milliseconds and has been stable and healthy

  ever since — doesn't appear related to the app's current outage

Two failed request IDs from the platform's own error page, if useful for

looking up server-side logs:

Sg740-UKRoq-1uKUN8N_Fg

h6qDeWTUTGGmcDJX5nX1uw

Nothing about my app's code changed between its last successful run this

morning and now — only database content was modified (via scripts run

against the database directly), no deployments happened in between until

I started troubleshooting this issue.