Hello Railway Team,

I need your help identifying what I'm doing wrong in my deployment

process. I'm consistently triggering double deployments (current +

previous commit) in one specific project, while all my other Railway

projects work perfectly fine.

The Situation:

- Problem Project: msrvbuchhaltung (MSRV Buchhaltung)

- Working Projects: Multiple other Railway projects with identical setup

- Branch: main

- Service: GitHub integration

What Happens:

When I push commit 990ec38, Railway deploys:

1. Commit 990ec38 → Deploys successfully

2. Commit bf60f05 (previous) → Crashes immediately

I receive "Deploy Crashed!" emails for the previous commit re-deploying.

Important Context:

- My other Railway projects work fine - no double deployments

- This project HAD the same issue before, and I fixed it

- Now the problem is back and I can't figure out what I'm doing

differently

- The first 1-2 pushes in a session work fine, then double deployments

start

What I've Verified (Not the Cause):

- No GitHub webhooks configured

- No GitHub Actions

- Clean git history (no force pushes, no amends)

- Railway settings are identical to my working projects

- Standard railway.json configuration

What I Need Help With:

Since my other Railway projects work perfectly and only THIS project has

the issue, there must be something I'm doing differently in my workflow or

code that triggers this behavior.

Questions for Railway Team:

1. Can you see in your deployment logs what's triggering the second

deployment? Is it a webhook, an API call, something else?

2. Is there a difference in how this project is configured vs. a normal

project? Maybe I accidentally enabled something?

3. Could you check if there are multiple deployment triggers configured

that I'm not seeing in the UI?

4. Are there any Railway CLI commands in my git history or hooks that

could be triggering extra deployments? (I don't think so, but maybe I'm

missing something)

5. What makes the first 1-2 pushes work correctly, then subsequent pushes

fail? Is there a state or cache that changes?

What Would Really Help:

If you could look at the deployment logs for project "MSRV Buchhaltung"

and tell me:

- What exactly triggers the second deployment

- If there's any difference in webhook payload or source between the two

deployments

- Any configuration on my project that's different from a standard GitHub

integration

My Theory:

I must be doing something in my development workflow that causes this, but

I can't figure out what. Since you can see the backend logs and webhook

data, you might be able to spot what I'm doing wrong.

I apologize for the trouble - I know this is my mistake, but I need help

identifying what it is.

Thank you for your patience and assistance!

Best regards

---

Project Details:

- Project: msrvbuchhaltung

- Environment: production

- Type: Next.js 16.0.1

- Database: PostgreSQL (separate