Skip to content
Auto-deploy not triggering after recent builds outage (project: cheerful-eagerness)
aleksandrakravchenko2004lilla
OP

a month ago

Hi, since your recent "New builds are temporarily paused" incident, auto-deploy on my production service has stopped working entirely.

•	Project: cheerful-eagerness, service: production

•	Source Repo is connected, branch main, Auto Deploy is enabled, Wait for CI is off

•	GitHub App (Railway App) is installed, not suspended, scoped to All repositories, with full read/write permissions

•	Several PRs have been merged into main since the incident (including an empty trigger commit), but none of them have produced a new deployment — the last active deployment is still from a merge that happened before the incident

•	No webhook delivery errors are visible on my end since I can't access delivery logs directly

Could you check whether GitHub push events for this repo/branch are actually reaching Railway's backend, and manually trigger a redeploy of the latest main commit in the meantime?

Repo: aleksandrakravchenko2004lilla/Frankkkkkk21

Last commit that should be deployed: 16de468 (and everything before it back to PR #205)

Thanks!

Solved

1 Reply

Railway
BOT

a month ago

Apologies for the trouble. Between 17:03 and 20:56 UTC on October 20 we had an incident that paused new builds. It has since been resolved. Pushes, merges and deploy triggers made during the pause were not queued, so they will not start on their own and need to be triggered again. You can see the full timeline here: New builds are temporarily paused.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

22 days 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 • 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...