2 hours ago
Hi Railway Support,
Please help clear stalled rollout state for our MindOS Flywheel deployment in flywheel-staging.
Project ID: c33393d2-c096-44c5-9cf4-b494e951cafb
Environment: flywheel-staging
Environment ID: 359fdbfe-642d-4d53-868d-e073f7fe626a
Service: mindos-flywheel (1f6bb995-de5f-448b-8233-76c43686e5b1)
Service domain: https://mindos-flywheel-flywheel-staging.up.railway.app
Current status is still stuck in INITIALIZING with no running instances:
- Latest deployment: 5b7eed48-e9cd-499a-939e-c15288dbf558
- Created: 2026-09-14T00:57:29.869Z
- Service shows: configured replicas: 1, running replicas: 0, deploymentStopped: true
- Domain still returns Railway fallback 404
Observed related deployment history:
- 5b7eed48-e9cd-499a-939e-c15288dbf558 — INITIALIZING (stuck)
- 03422dfa-9018-4dab-a452-9795c1439263 — INITIALIZING (stuck)
- 26daab8b-7370-454a-a915-c25af939a865 — INITIALIZING
- 3d4ae931-5ad2-476c-bfcc-e727d968a332 — FAILED
- ff1b995b-77ab-4846-8e32-55220e870d3a — FAILED
- 74074de5-5ce2-440f-b99e-a347455e4b56 — FAILED
Last visible build-level failure before this state was:
couldn't locate the dockerfile at path services/mindos-flywheel/Dockerfile in code archive.
Current deploy configuration on these attempts:
- builder: DOCKERFILE
- dockerfilePath: services/mindos-flywheel/Dockerfile
- preDeployCommand: /usr/local/bin/mindos-flywheel-migrate
- healthcheckPath: /healthz
Actions already taken:
- Reconnected service source to bbshocking/mindosv3 on master
- Tried explicit redeploy via railway up --no-gitignore (and retries)
- Tried service scale 0→1 and source reconnect/redeploy sequences
- No local CLI path can clear or restart this stuck rollout
Please inspect and clear any stuck/stale rollout/deployment state so we can run one final targeted redeploy cleanly.
Thanks.
1 Replies
2 hours ago
There is no stalled rollout state to clear - the deploy backlog is empty and nothing is holding a build or deploy slot. The deployments you listed completed as FAILED with two distinct errors. The earlier three failed at the build step because services/mindos-flywheel/Dockerfile could not be found in the code archive. The later three never reached a build - they timed out at the code snapshot step with "Failed to create code snapshot," meaning the platform could not package the repo contents into a build archive. Verify that services/mindos-flywheel/Dockerfile exists at that exact path in the connected branch of your repo, then trigger a fresh deploy.
Status changed to Awaiting User Response Railway • about 2 hours ago
Status changed to Solved bbshocking • 11 minutes ago