Check if you have selected the same branch you are making changes to, in your service settings > source.

nope that's set correctly

Hi. You should've gotten an email and notification recently. You need to accept new permissions of your Railway App in GitHub. These permissions are required to ensure code access of project members.

You can do the following:

1. Go into your Organization settings
2. In the sidebar, navigate to "GitHub Apps"
3. You should see Railway App in the list, with an information along the lines "new permissions requested" or similar
4. Click on "Review" and confirm
5. After doing so, you may also need to disconnect and reconnect the repo in your service.

Thanks @timomeh!

Took a look — Railway App on my GitHub doesn't show any "Permission updates requested" banner, all permissions are already green-ticked (read+write to actions, administration, checks, code, commit statuses, deployments, pull requests, workflows). narumaam/nama-frontend is in the selected-repos list. Installed last month.

I've also already done the disconnect-and-reconnect dance on the Railway side — both the branch alone and the entire Source Repo card. Warning persists. Pushed an empty test commit (278473c) to confirm: Vercel auto-deployed, Railway didn't.

One thing that might be relevant: this service (intuitive-blessing) was originally created via railway up from CLI before being linked to GitHub. Could that be confusing Railway's internal state about which path should drive deploys? Happy to share the project ID if it helps you check from your side.

Could you try to click "Add" on the canvas, then select GitHub Repositories in the command palette that appears, and then click on the "Refresh" button? (see attached screenshot 1)

It seems like our cache is out-of-sync. We currently have your repo tracked as a public repo without an installation. You can see this as indicated "Auto deploy unavailable" (see screenshot 2)

It would be helpful to know if refreshing the repos on your end fixes this.

To your question, railway up doesn't interfere with autodeploys from GitHub. The issue here is purely that we currently don't associate the repo with your installation.

Timomeh, Followed your steps — clicked + Add on the canvas, opened the GitHub Repositories palette, clicked the Refresh button. Palette re-loaded and narumaam/nama-frontend showed up correctly. Closed the palette, went back to intuitive-blessing → Settings, but "Auto deploy unavailable" warning is still there. No change after refresh.

Anything else to try from my end? I can attempt a full uninstall + reinstall of the Railway App from GitHub, but wanted to check before I touch that since it'd affect the link to the existing service. Project: zoological-commitment, service: intuitive-blessing.

I found and fixed the underlying issue in our GitHub Repo sync. You should now see that it doesn't anymore show "Auto deploy unavailable", and you can click on "Enable". Then autodeploy should work as expected again.

Apologies for the inconvenience, and thanks for the cooperation!

Update: clicked Enabled, that flipped the toggle correctly. The very next backend commit I pushed (12ec98b, ~15 min ago, touches backend/app/api/v1/predictions.py) was NOT picked up — Active deployment in Railway is still test: verify Railway auto-deploy from 2 hours ago. So auto-deploy fired ONCE after your sync fix, but hasn't fired again on subsequent pushes.

Vercel auto-deployed 12ec98b cleanly from the same push, just for reference — so the GitHub side is sending the webhook fine, something on Railway's side still isn't picking it up.

Project zoological-commitment / service intuitive-blessing / branch main. The "Auto deploys when pushed to GitHub" toggle is currently set to Enabled. Anything else I should check / disable / re-enable from my side?

I'm running railway up to get this commit live in the meantime — so don't be alarmed by a "via CLI" deployment from me. Just need the auto-deploy itself to be reliable for normal use.

From what I can see in the logs, autodeployment was enabled after we received the push from GitHub. Meaning at the time of the push, autodeployment wasn't enabled, and it didn't autodeploy. Can you try again?

Update: pushing again now (commit fixes a related bug we found while verifying P0 audit fixes — slowapi Limiter wasn't sharing instances between main.py and routers). Will report back whether Railway picks up the new push automatically. Project zoological-commitment / service intuitive-blessing / branch main.

Confirmed — auto-deploy is now working end-to-end. Pushed commit eacf751 (P1-A bugfix), Railway auto-built it via GitHub (no railway up needed), deployment is ACTIVE. Verified live: ✓ /api/v1/health green ✓ POST /api/v1/register-user (audit P0-1 fix) returns 422 as expected ✓ /api/v1/webhooks/razorpay (legacy) returns 404 as expected ✓ /api/v1/payments/webhooks/razorpay (new) returns 400 sig-missing Thanks for the persistence on this one — the cache-sync fix on your end + clicking Enable did the trick. Closing the loop on the thread.

Glad to hear it's all working now. Thanks for confirming and for your patience while we tracked it down!