Subject: Service stuck deploying a commit that no longer exists in my GitHub repo

Hi, my service "petflix-automation" (project: PetFlix automation Bot WhatsApp) is stuck.

The problem: the active deployment is running commit 07e6c6fa, but this commit does NOT exist in my GitHub repository at all — it doesn't appear in git ls-remote origin.

My setup is correct as far as I can tell:

• Settings > Source is connected to the right GitHub repo
• Settings > Branch is set to "main"
• The remote main branch (origin/main) points to commit bcd18ae (verified via git ls-remote)
• GitHub has the correct, latest code

But Railway keeps deploying the old/phantom commit 07e6c6fa instead of bcd18ae. I have tried:

• Redeploy (just repeats the old commit)
• Pushing a new empty commit to main
• Changing the branch and switching back to main
• Disconnecting and reconnecting the GitHub repository

None of these made Railway pick up the latest commit (bcd18ae) from main. It seems the GitHub <> Railway sync is stuck in an inconsistent state.

Could you please force my service to deploy the current HEAD of main (bcd18ae), or reset the GitHub connection on your side? The service is in production, so I'd appreciate help avoiding downtime.

Thank you.