Subject: Pro Plan Escalation — Railway Building From Stale Snapshot, Ignoring GitHub Source

Hi Railway Support,

I am a Pro plan subscriber writing to escalate a confirmed infrastructure issue. I need engineering-level intervention — this cannot be resolved from the user side.

THE PROBLEM:

Railway is building Rhapsody from a stale internal snapshot rather than pulling fresh code from our connected GitHub repository. Every redeploy serves old code regardless of what we do.

EVIDENCE — TWO CONSECUTIVE BUILD LOGS SHOW IDENTICAL SNAPSHOT:

Build 1 (11:10 AM GMT+2, deployment 484e69a0):

unpacking archive 350 KB 2ms

uploading snapshot 92.1 KB

Build 2 (11:21 AM GMT+2, deployment e1d7805c):

unpacking archive 350 KB 3ms

uploading snapshot 92.1 KB

The archive size is identical across both builds — 350 KB / 92.1 KB — despite multiple new commits being pushed to the repository between these deploys. Railway is not fetching from GitHub. It is repeatedly building from a cached internal snapshot.

STEPS ALREADY TAKEN (none resolved the issue):

• Set NO_CACHE=1 environment variable → caching confirmed disabled (🚂 Caching Disabled shown in logs), but snapshot remains stale
• Disconnected and reconnected GitHub repository
• Triggered multiple manual redeploys
• Used Deploy Latest Commit from Command Palette
• Railway's own support Agent confirmed: "This is a legitimate infrastructure issue that requires backend access. Railway support should be able to resolve it in minutes."

IMPACT:

This is a production application serving a paying client. We have bug fixes and feature updates that cannot be delivered while Railway continues to build from a stale snapshot. This has been blocked for multiple days.

ACTION REQUIRED:

Please have your engineering team locate and purge the stale snapshot stored on your Metal builder infrastructure for this service, and force a clean fetch from GitHub HEAD.

Thank you,

Henry van der Berg

vanderberg.henry@gmail.com