Getting false "Deploy Crashed!" emails during normal deployments
mickythompson
FREEOP

4 months ago

Hey team! I'm getting "Deploy Crashed!" emails every time I deploy, but my deployments are actually successful.

Project ID: 02925e76-7600-48bc-99ec-42b7230f0079

What's happening:

  • Deploy new version to staging

  • New container starts successfully

  • Old container shows "Stopping Container" in logs

  • I get a "Deploy Crashed!" email

  • But the new deployment is running fine (confirmed via health endpoint)

Details:

  • Using Railpack

  • Using RAILWAYBETAENABLERUNTIMEV2=1

  • NestJS API service

  • Deployment teardown settings: 60s overlap, 30s draining

Is this a known issue with the old container shutdown being misinterpreted as a crash? The API is working perfectly, just getting false crash notifications.

Solved

7 Replies

angelo-railway
EMPLOYEE

4 months ago

Hey @Micky Thompson - what happens when you remove this variable?

RAILWAY_BETA_ENABLE_RUNTIME_V2=1

angelo-railway
EMPLOYEE

4 months ago

Customers usually see this whenever the service exits with a non-zero exit code, but I swear that we solved this issue a while ago.

brody
EMPLOYEE

4 months ago

-# The V2 runtime isn't beta anymore, and it is currently the only available runtime, so that var would be a no-op.

But this can happen when a Node application is run via npm, yarn, or pnpm. Can you try changing your start command from yarn start:api to node dist/main within your start command in the service settings?

angelo-railway
EMPLOYEE

4 months ago

lol fair

mickythompson
FREEOP

4 months ago

Thanks for the suggestion! Executing the compiled application directly instead of using the package script worked perfectly.

brody
EMPLOYEE

4 months ago

Awesome!

brody
EMPLOYEE

4 months ago

!s

Status changed to Solved brody • 4 months ago

Loading...