---

Subject: GitHub-connected service keeps deploying an old commit instead of branch HEAD

Project: virtuous-amazement / production

Service: future-ip-website-v2

Repo: Richardvandev/future-ip-website-v2

Branch connected to production: main

Auto-deploy: enabled, Wait for CI: off

Problem:

Every deployment (including manual "Redeploy" and pushes) builds an OLD

commit ("Privacy: Railway-hosting + dataopslag binnen EU (Amsterdam)..."),

instead of the current HEAD of main. The branch HEAD on GitHub is several

commits ahead and contains the changes I need deployed.

Current GitHub main history (newest first):

• e31eb00 Force rebuild: directe offerte live zetten (build marker)
• 392c38e chore: trigger Railway redeploy (directe offerte)
• 297061a Directe offerte: offerte maken zonder eerst volledig opnameformulier
• 177720d Privacy: Railway-hosting + dataopslag binnen EU (Amsterdam)... <-- Railway keeps deploying THIS one

What I already tried (none worked):

• Manual "Redeploy" multiple times
• Pushing an empty commit
• Pushing a new commit with real file changes
• Disconnecting and reconnecting the branch (main)
• Fully disconnecting and reconnecting the GitHub repo + branch main

After every attempt, the new deployment still shows the old "Privacy" commit

and "Deployment successful", but the running code is the old version

(new endpoint /api/opname/direct returns 404, new frontend code is absent).

Note: this started around the time of a Railway incident ("Logs and metrics

may be slow to load"). The service was recently migrated to EU West (Amsterdam).

Request:

Please force this service to deploy the current HEAD of main (commit e31eb00),

or fix whatever is pinning it to the old commit 177720d. Thank you.