what is not working exactly? do you get any errors on your build/deploy logs?

Yes

I will show you

Got it. I'll step back and let them take point. I've documented everything they need:

Service ID: edb04711-fcdd-426e-906d-76c496c8939d

3 failed deployment IDs: f1dfb083, 0a70ca01, 26b751fb

Pattern: Zero logs at orchestration layer, no CREATE_CONTAINER event, code is clean

Last successful: b888ff79 (still online)

Let me know if you need me to pull any additional data or logs for them.

what kind of app you're trying to deploy?

The ticket — paste this at station.railway.com

Service: Nomni-Ninja-Hub-Main · project 43008532 · env production

Symptom: Since ~07:36 UTC 2026-07-14, every git-triggered deploy fails instantly: zero build logs, zero deploy logs, zero events, failureStage/failureError null (confirmed by your own conductor agent — "never reach SNAPSHOT_CODE, rejected at orchestration").

Controlled experiment (rules out our code): commit 60cd38dd6 git-deployed successfully at 06:49 UTC (deployment b888ff79). The same commit, re-deployed via serviceInstanceDeployV2 at 19:08 UTC with nothing in flight → deployment a6cf0013 FAILED, zero logs. Identical code, opposite outcome.

Builder is healthy: direct uploads (railway up) build and deploy fine on this same service (8d872279, SUCCESS 17:29 UTC). Only the GitHub-fetch path dies.

Failing deployment IDs: a6cf0013, 9816e00f, cd53b930, d1a11800, 586ba883 (earlier: f1dfb083, 0a70ca01, 26b751fb, 18239db4).

Please check: orchestration/admission logs for this service, and the GitHub App installation/token state for Liven-Group/Nomni-Ninja-Hub (repo is 74MB checkout / ~800MB history — same weight when it worked at 06:49).

Try uninstall and reinstall the Github App, and try disconnect and reconnect the repo after reinstall

I did it but it keeps failing. It keeps saying

This deployment was cancelled before any build started, which is why there are zero build logs, zero deploy logs, and no recorded failure stage. This matches a well-documented pattern on this service where overlapping deploy triggers supersede each other, and Railway records the cancelled one as FAILED. Trigger a single fresh deployment on main and wait for it to reach a terminal status before pushing again or running railway up.

the build doesn't even start. For context I changed the memory and cpu stuff before and also I was told my repo is too large so I deleted some - but untill 4pm monday it was working then my ai says if its our code then it would work if we push the last commit that worked before but right now we pushed that also doesn't work ai says shows that its not our code its railway but I am not sure - how do I get help from the railway people then?

how do I get help from the railway people?

iirc, you can create a private thread since you're on the pro plan (if you mean railway people means railway staff)

so it didn't even success to fetch the repo, is this repo moved to an orgs? you may need to install the Railway App on the orgs too, or try create another service with same repo as the source