Summary:

Changes pushed to our GitHub repository are not triggering CI or automatic deployments in Railway. When deployments are run, the build appears to use a stale copy of the repository rather than the latest commit.

Expected behavior:

Each push to the configured branch should trigger a new deployment using the latest commit from the repo.

Actual behavior:

• Git pushes do not trigger a deployment
• Manual redeploys sometimes occur, but the build uses an older commit/state of the repo
• Commit SHA in Railway does not match the latest SHA in GitHub

Troubleshooting already performed:

• Verified correct repo and branch are configured in Railway
• Confirmed Railway GitHub App has access to the repository
• Cleared build cache and redeployed
• Manually triggered redeploys
• Deleted and recreated:
  • Railway service
  • Railway ↔ GitHub connector / app installation
• Reconnected repo from scratch after deletion
• Verified latest commits exist on the target branch in GitHub

Current state:

Even after fully removing and re-adding the GitHub integration and service, Railway continues to behave as if it is building from a cached or stale repo state, and pushes do not trigger CI.

Request:

Please investigate whether there is a stuck cache, webhook/app event issue, or internal state mismatch on the Railway side preventing GitHub push events from triggering fresh builds. Assistance resetting or validating the backend integration state would be appreciated.