Skip to content

Railway Deployment Not Triggering After October 21 Incident

Anonymous
OP

24 days ago

Hello Railway Support Team,

I'm experiencing an issue with my Railway service, iron-paradise-gym-management-system. My latest GitHub commit is not triggering a new deployment.

Project details:

  • Branch: main
  • Latest commit: e99b637 — feat(reminders): add concurrency safety and manual expiry fix
  • Current active deployment commit: 8045dec — Fix WhatsApp template language configuration
  • Environment: production
  • Root directory: /backend

Steps I've already tried:

  1. Verified that commit e99b637 exists on GitHub's main branch.
  2. Confirmed that the Railway GitHub App has access to the repository.
  3. Confirmed that the correct repository and main branch are connected in Railway.
  4. Disconnected and reconnected the GitHub repository in Railway.
  5. Used Ctrl+K → Deploy Latest Commit, but it returns me to the existing deployment instead of creating a new one.

No new deployment appears in the deployment history, and the service continues running the older commit.

I also noticed a Railway activity entry showing that the Commit SHA and Upstream URL settings were cleared. I'm unsure whether this is related to the October 21 incident.

I found the recovery guidance stating that commits pushed while deployments were paused were not queued and require a manual deployment. However, the recommended manual deployment procedure has not worked for my service.

Could you please investigate why Railway is not detecting my latest commit or creating a new deployment?

Thank you for your help.

Solved

4 Replies

Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

The commit you pushed on October 24 at 07:18 UTC was refused by the deploy pause that followed the October 21 incident, so it was never queued, which is why the service still runs the older commit. Full steps for recovering deploys after the pause: https://blog.railway.com/p/security-disclosure-recommendation-recover-failing-deploys

Your environment also has a staged change from 07:52 UTC today, the repository reconnection, that hasn't been deployed yet. Click Deploy on the changes bar at the top of the project canvas to apply it; that creates a fresh deployment from the latest commit on the connected branch. The cleared Commit SHA and Upstream URL entries in the activity log are the normal result of disconnecting and reconnecting the repository, not something the incident did. If the deploy is refused, reply with the exact message you see and the deployment ID.


Status changed to Awaiting User Response Railway • 24 days ago


dizzydes90

The commit you pushed on October 24 at 07:18 UTC was refused by the deploy pause that followed the October 21 incident, so it was never queued, which is why the service still runs the older commit. Full steps for recovering deploys after the pause: https://blog.railway.com/p/security-disclosure-recommendation-recover-failing-deploys Your environment also has a staged change from 07:52 UTC today, the repository reconnection, that hasn't been deployed yet. Click Deploy on the changes bar at the top of the project canvas to apply it; that creates a fresh deployment from the latest commit on the connected branch. The cleared Commit SHA and Upstream URL entries in the activity log are the normal result of disconnecting and reconnecting the repository, not something the incident did. If the deploy is refused, reply with the exact message you see and the deployment ID.

Anonymous
OP

24 days ago

Hi, thanks for your help.

I checked the project canvas, but I cannot find a pending-changes bar or a Deploy button. The activity entry only shows “2 changes applied” for Commit SHA and Upstream URL, with blank new values.

The repository is currently connected to the correct GitHub repository and main branch, but no new deployment has appeared. I also tried Ctrl+K → Deploy Latest Commit, without success.

Could you please guide me on how to apply the staged change or trigger a fresh deployment? I don't want to make further configuration changes without confirmation.

image.png

image.png


Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

The change we pointed you at turns out to be empty, which is why there's no Deploy bar to click. It was created at 07:52 UTC today when the repository was reconnected and contains no settings, so there's nothing for you to apply. The "2 changes applied" entry in your screenshot is the earlier one from October 24, when the old commit pin and upstream URL were cleared by the reconnect, and that's expected.

Your workspace is no longer under the deploy pause, so the quickest way to get e99b637 live is to push a new commit to main (an empty commit is fine). That goes through the normal GitHub trigger and should show up in the deployment list within a minute or so.

If nothing appears after the push, reply with the time you pushed and we'll trace it from our side.


Status changed to Awaiting User Response Railway • 24 days ago


Anonymous
OP

24 days ago

It's done . Thanks :)


Status changed to Awaiting Railway Response Railway • 24 days ago


Status changed to Solved Anonymous • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...