DATABASE_URL edits via Dashboard do not persist (single-field editor and Raw Editor, 3 attempts) on @investpro/server
diegolcirqueira
FREEOP

18 days ago

Summary: Editing the DATABASE_URL variable on our @investpro/server service (production environment) through the Dashboard does not persist the new value, even though CLI/API writes to other variables on the same service work correctly.

Project ID: 362bbc0f-de1f-4f9f-aa02-214098f4bc3a (easygoing-patience)

Service ID: d46c09ca-5601-448d-9801-3da41c085afd (investpro/server)

Environment ID: 949c03ff-607b-413a-b60f-a9ec717b4966 (production)

Steps we took (3 attempts total): edited DATABASE_URL via the single-field variable editor twice, and via the Raw Editor once. After each attempt we independently confirmed via two methods -- railway variables --kv (CLI) and a direct GraphQL query to the Railway API, no cache -- that the value still shows the old placeholder username (postgres.xxxxxxxx), not the corrected connection string.

What we ruled out: wrong project/service/environment (IDs above match exactly what the CLI reports and what appears in the Dashboard URL), a shared-variable reference overriding it (the raw value is a literal string, not a double-curly-brace service reference), a duplicate or similarly-named variable, a native Railway integration or webhook rewriting it (the integrations query for this project returns an empty list), and a GitHub Actions workflow in our repo touching Railway (none found). A leftover native Postgres plugin exists in the same project but DATABASE_URL correctly targets our external Supabase host, unrelated.

Contrast: we successfully rotated JWT_SECRET and JWT_REFRESH_SECRET on this same service via the CLI (variables set with stdin), and those changes persisted immediately and correctly. Only DATABASE_URL, and only via the Dashboard, fails to persist.

Impact: no current outage -- the last successful deployment from around Sep 10 keeps serving traffic -- but we cannot ship any new deploy of this service until DATABASE_URL can be corrected.

Question: why would edits to this specific variable, on this specific service, not persist from the Dashboard (both the single-field editor and Raw Editor), while CLI writes to other variables on the same service work normally? Happy to provide deployment IDs, timestamps, or a screen recording if useful.

$10 Bounty

2 Replies

Railway
BOT

18 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 18 days ago


Did you redeploy after altering the variable on the dashboard?


When you change a variable through the dashboard, a "Deploy" button appears at the top of the canvas. Make sure you press it to apply changes.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...