2 hours ago
For a service configured with one replica, Railway Console initially showed “Connected” and allowed Files to be opened. Minutes later, the same view showed “No running instances” and “Disconnected”.
A subsequent environment status query reported one active replica.
Can Console show “No running instances” while the service has an active replica?
What conditions determine instance selection or availability in Console?
Is there an official, non-destructive procedure, without a restart or redeploy, to restore access to the file browser?
We are not requesting changes to be executed or access to the service data.
1 Replies
2 hours ago
Yes, the two can disagree. Console only counts an instance as available while that instance reports a running state. A replica count, or a deployment marked active, is not the same check. If the instance is restarting, still starting up, or has exited, Console shows "No running instances" and turns off the terminal, even though the environment still lists one replica.
When an instance is running, Console connects to the one you picked in the instance selector. If you haven't picked one, or your pick is no longer running, it uses the first running instance. "Disconnected" is a separate state: it means the live connection to that instance closed or failed.
To get access back without restarting or redeploying, use the Reconnect button that appears in the Console header when it shows Disconnected. The Files panel has its own Reconnect button when it shows "Connection lost". Reloading the page refreshes the instance list, and you can then reconnect. Neither step changes the service. Reconnecting only works once the instance reports as running again. If it doesn't, the instance itself has stopped running, and you can see why in the service's deployment logs.
Status changed to Awaiting User Response Railway • about 2 hours ago