Railway config pull fails with “planning returned diagnostics” when importing existing project

a month ago

railway config pull cannot import an existing linked project containing web and worker GitHub services using Dockerfile builds, plus Postgres and Redis database services.

NOTE: I'm using a monorepo structure with turporepo

Reproduction:


railway --version # railway 5.5.0

pnpm list railway # railway 3.1.1

railway link # linked to existing project

railway config pull

Result:

Could not import Railway configuration because planning returned diagnostics.

Also fails with --force, --json, --force --json, and --force --agent.

Project Info:

  • web:
    • repo=bionboy/pad,
    • builder=DOCKERFILE,
    • dockerfilePath=apps/web/Dockerfile,
    • buildCommand="pnpm --filter @pad/web build",
    • healthcheckPath="/"
  • worker:
    • repo=bionboy/pad,
    • builder=DOCKERFILE,
    • dockerfilePath=apps/worker/Dockerfile,
    • buildCommand="pnpm --filter @pad/worker build",
    • startCommand="node --import ./instrument.mjs dist/index.js"
  • Postgres:
    • image=ghcr.io/railwayapp-templates/postgres-ssl:18,
    • mount=/var/lib/postgresql/data
  • Redis:
    • image=redis:8.2.1,
    • mount=/data

Expected: railway config pull writes .railway/railway.ts matching current state, or prints the specific planning diagnostics.

Actual: import aborts with only the generic error above.

Solved

1 Replies

Railway
BOT

a month ago

Infrastructure as Code is still experimental, and the "planning returned diagnostics" error is a known gap where the CLI does not surface the specific diagnostics that caused the import to fail. One common trigger is services in the project that are already managed by a railway.json or railway.toml file, since IaC and Config as Code cannot manage the same service simultaneously. If any of your services have a config-as-code file, removing or clearing the config file path in each service's settings before running railway config pull should unblock the import. If you don't have any config-as-code files, this may be a CLI bug with the importer for your project shape (Dockerfile builds with custom paths in a monorepo plus database services with volumes), and we'd recommend opening an issue on the CLI repo so the team can reproduce it with details about your project structure.


Status changed to Awaiting User Response Railway 29 days ago


Railway
BOT

22 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...