I’m seeing behavior that looks like an automatic rollback, and I want to confirm what triggered it. ## Setup * Railway project: `profound-smile` * Environment: `production` * Service: `digest-agent` * Deployments are triggered from GitHub `main` branch ## What happened * On **2026-02-05**, deployment `9ded0bed-860a-45a4-add5-0e37a58478e8` was created from commit `b5445d38a8aa9ed74a23cd4c0b74c07c31ef6286` with `meta.reason = "deploy"`. * Later, this deployment became `REMOVED`. * On **2026-02-12**, deployment `0addd8c6-77a8-4254-9d6c-1981c24f85df` became active with commit `5fcfffcc9f6a26bbbac33679cce3af451d344c8d` and `meta.reason = "redeploy"`. * Screenshot attached in the first comment. ## Expected * I expected the latest commit deployment `b5445d3...`) to remain active unless a new push to `main` happened. ## Observed * An older commit (`5fcfffc...`) became active via a redeploy event, and the newer deployment was marked `REMOVED`. * Build/deploy logs for both deployments look normal (no crash loop or healthcheck failure indicating automatic rollback). ## Question What actor/action triggered deployment `0addd8c6...` and why it selected commit `5fcfffc...` instead of current `main` head?

Unexpected redeploy of older commit replaced latest GitHub deployment

agdhruv

HOBBYOP

5 months ago

I’m seeing behavior that looks like an automatic rollback, and I want to confirm what triggered it.

Setup

Railway project: profound-smile
Environment: production
Service: digest-agent
Deployments are triggered from GitHub main branch

What happened

On 2026-02-05, deployment 9ded0bed-860a-45a4-add5-0e37a58478e8 was created from commit b5445d38a8aa9ed74a23cd4c0b74c07c31ef6286 with meta.reason = "deploy".
Later, this deployment became REMOVED.
On 2026-02-12, deployment 0addd8c6-77a8-4254-9d6c-1981c24f85df became active with commit 5fcfffcc9f6a26bbbac33679cce3af451d344c8d and meta.reason = "redeploy".
Screenshot attached in the first comment.

Expected

I expected the latest commit deployment b5445d3...) to remain active unless a new push to main happened.

Observed

An older commit (5fcfffc...) became active via a redeploy event, and the newer deployment was marked REMOVED.
Build/deploy logs for both deployments look normal (no crash loop or healthcheck failure indicating automatic rollback).

Question

What actor/action triggered deployment 0addd8c6... and why it selected commit 5fcfffc... instead of current main head?

Solved

2 Replies

agdhruv

HOBBYOP

5 months ago

Screenshot attached.

Attachments

ss.png

brody

EMPLOYEE

5 months ago

Hello,

The redeploy itself was caused by maintenance on an underlying host. This is something that can happen from time to time.

https://docs.railway.com/deployments/reference#railway-initiated-deployments

As for why that deployed older code, we are not sure at this time, but I have created a ticket for us to look into if we get further similar reports from our users.

Status changed to Awaiting User Response Railway • 5 months ago

Railway

BOT

4 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 • 4 months ago

Welcome!