GitHub autodeploy not triggering for one specific repository — no deployment record created

Project: rush-crm (6ea1a117-eaf3-4de9-9e74-89589be7184f)

Environment: production (ca2aa13f-b4a9-4bc7-9578-c8e162e6fc4f)

Services: rush-crm (883ae46c-5092-491d-8579-4ba02b2a36d1) and alluring-elegance (83b6e0d6-cc32-4e49-b8a5-3095ba3feb51)

Repository: nextgo-ship-it/rush-crm

Branch: main

Commit not deployed: f850a11 (merge of PR #1), pushed 2026-08-04 around 23:30 UTC.

The last automatic deployment on both services was 2026-06-29T04:10Z (commit 8d7c70e). Since then, no push to main has ever triggered a deployment.

What I verified:

• Autodeploy is enabled ("Auto deploys when pushed to GitHub"), branch main is connected, Wait for CI is off.
• No SKIPPED deployments exist in this project (checked via API filtering by status).
• No watch paths configured.
• Railway GitHub App is installed on the account nextgo-ship-it with "All repositories" access and read+write on code, deployments, checks.
• Another project in the same workspace, nextgo-crm, connected to the repository nextgo-ship-it/nextgo-crm, autodeploys normally — most recently 2026-08-05T00:10Z. So the integration works in general; it fails only for rush-crm.

What I already tried, without success:

• Disconnecting and reconnecting the branch in Service Settings.
• Disconnecting and reconnecting the whole source repository in Service Settings.
• Changing an environment variable to force a deployment.

Workaround that does work: railway redeploy --from-source --yes deploys the correct commit.

This looks like the internal link between the service and the current GitHub App installation is stale, similar to other reports on Central Station. Could you please re-link services 883ae46c-5092-491d-8579-4ba02b2a36d1 and 83b6e0d6-cc32-4e49-b8a5-3095ba3feb51 to the current GitHub App installation so that push events are matched again?