GitHub-connected service not creating deployments after new commits (staging branch)
unityspace-repo
HOBBYOP

a month ago

Project/Service:

  • Project: <your project name>
  • Service: Frontend (existing production/staging service)
  • Source: GitHub repo UnitySpace-Repo/UnitySpace
  • Branch: staging

Issue summary: Our frontend service is connected to the correct GitHub repo/branch, but Railway is not creating any new deployment records from recent commits to staging.

Observed behavior:

  • Last visible deployments are old:
    • 21705e26 – Failed
    • 0946122a – Failed (snapshot step showed ##NOT-AUTHORIZED## repository not authorized)
    • 80c5e29e – Active
  • No new deployments appear after multiple successful pushes and empty redeploy-trigger commits.
  • In GitHub, staging and feature/exhibition-management show recent pushes.
  • We disconnected/reconnected source repo in Railway, but still no new deployment objects were created.

Recent commits pushed to staging (confirmed on origin):

  • e004660 – fix JSX conditional in public booking page
  • 2c5b8ed – chore: trigger staging redeploy
  • 464e5e4 – chore: trigger staging redeploy (retry 2)

What we already tried:

  1. Verified repo + branch mapping in Railway Source settings (correct).
  2. Re-authenticated GitHub in browser.
  3. Disconnected/reconnected same repo+branch in Railway.
  4. Pushed multiple new commits (including empty commits) to force webhook-triggered deployment.
  5. Confirmed commits are present on origin/staging.

Expected behavior: Each push to staging should create a new deployment record automatically.

Actual behavior: No new deployment records are created at all after old records above.

Request: Please check and reset/rebind GitHub webhook/integration state for this Railway service and investigate why deploy trigger ingestion is stuck for this service.

Solved

6 Replies

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

unityspace-repo
HOBBYOP

a month ago

  • Redeploying old deployment 21705e26 runs and fails with old JSX syntax error.
  • Latest staging has fix commit e004660 (plus 2c5b8ed, 464e5e4), but those commits never appear as deployments.
  • Therefore Railway is not ingesting latest GitHub branch state for this service.
brody
EMPLOYEE

a month ago

Hello,

Can you make sure you have given the Railway App bot access to your repositories?

GitHub Settings -> Applications -> Railway App -> Configure -> Repository access

Then please go into your Railway account and unlink and relink the GitHub integration.

Best,

The Railway Team

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

unityspace-repo
HOBBYOP

a month ago

We’re blocked by deploy triggers not being created for one service.

  • Service source is connected to GitHub repo + staging branch.
  • Pushes are reaching GitHub (latest commit hash: b2f47dc).
  • No new deployment record appears in Railway after pushes.
  • Repo Access granted on Github. Checked and confirmed.
  • Reconnected GitHub integration and source mapping, then pushed again — same result.
  • Last visible deployment is an older failed one; nothing new gets created.

Could you please check trigger/webhook ingestion for this project/service and advise next steps?

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

unityspace-repo
HOBBYOP

a month ago

Below is the exact steps i followed:

  1. Verified Railway GitHub App repo access (UnitySpace-Repo/UnitySpace) in GitHub app config.
  2. Unlinked and relinked GitHub integration in Railway account.
  3. Reconnected source on frontend service to staging.
  4. Pushed a fresh commit (b2f47dc) to force a trigger.

Result: still no new deployment record is created in Railway after push.

So the integration appears connected in UI, but push events are still not being ingested for deployment creation.

Could you please check and reset/rebind webhook/trigger ingestion for this service from your side?

timomeh
EMPLOYEE

a month ago

Hi, I'm on the product engineering team and looked into this issue. I looked into your event history and saw that your webhooks are correctly configured.

The commits you mentioned were not deployed because of your watch paths configuration: if you push a commit that has no changes to files in your watch paths, there will be no new deployment. Your commits to re-trigger a deployment had no changes in no files - they were empty commits. Together with your watch paths configuration, these commits will be skipped and not be deployed.

Commit b2f47dc is on branch feature/exhibition-management. Your service is connected to the staging branch. So no new deployment was created.

Commit e004660 was indeed received, but the build failed with an intermittent error: https://railway.com/project/78defcb2-6b20-4e54-95a0-df868a922992/service/02eab8fb-ff67-444d-8bd6-ba7caf50f8ed?environmentId=af21a163-2934-4dd1-9a43-6465b1a82680&id=0946122a-9007-4690-8ed4-7fd3ebc26aa4#details

It looks like everything is working, except for the "Not Authorized" error which seems to be resolved. I can see that recent pushes were built and deployed.

Status changed to Awaiting User Response Railway • 29 days ago

timomeh
EMPLOYEE

a month ago

I'm going to move this to solved. If there are still issues, you can respond and reopen.

Status changed to Solved timomeh • 29 days ago

Welcome!

Sign in to your Railway account to join the conversation.

Login
Loading...