My service 'worker' in project 'harmonious-balance' (project ID 4ff68611-64fd-462c-9fc0-89088ea8fc76, service ID af0eeba1-b15f-4ce6-b4ba-827a0f62c9b2) has two related problems: 1. New deployments have been stuck in QUEUED for 30+ minutes with the message 'Deployment queued due to upstream GitHub issues.' I saw other users posting the same symptom in the last hour, so this may be a wider incident. 2. Separately, in Settings > Regions & Replicas, I see: 'Invalid region sfo is configured on this service and is blocking deployments. Pick a replacement region below — your workspace's default is pre-selected.' However, no region picker is shown because 'Replicas are not available for attached volumes' (this service has a volume attached for persistent SQLite data). So I have no way to fix the invalid region myself. Could someone please manually correct the region on this service to a valid one (e.g. the workspace default / us-west) without affecting the attached volume/data? The service is currently running on an old deployment (Active, ~15 hours old) so it's not down, but I can't ship new code. Thanks!

Deployments stuck in QUEUED - invalid region 'sfo' blocking deploys, can't fix via UI due to attached volume

elihelman

FREEOP

a month ago

My service 'worker' in project 'harmonious-balance' (project ID 4ff68611-64fd-462c-9fc0-89088ea8fc76, service ID af0eeba1-b15f-4ce6-b4ba-827a0f62c9b2) has two related problems:

New deployments have been stuck in QUEUED for 30+ minutes with the message 'Deployment queued due to upstream GitHub issues.' I saw other users posting the same symptom in the last hour, so this may be a wider incident.
Separately, in Settings > Regions & Replicas, I see: 'Invalid region sfo is configured on this service and is blocking deployments. Pick a replacement region below — your workspace's default is pre-selected.' However, no region picker is shown because 'Replicas are not available for attached volumes' (this service has a volume attached for persistent SQLite data). So I have no way to fix the invalid region myself.

Could someone please manually correct the region on this service to a valid one (e.g. the workspace default / us-west) without affecting the attached volume/data? The service is currently running on an old deployment (Active, ~15 hours old) so it's not down, but I can't ship new code.

Thanks!

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 30 days ago

sam-a

EMPLOYEE

a month ago

On the first issue: you were right that it was a wider incident. Our deploy queue backed up today (the GitHub message was misleading, it was on our side), and it has been fully cleared. Your latest deployment built and went live at 19:09 UTC, so new code is shipping again.

On the invalid region "sfo" warning: since your deploy just succeeded, it is not currently blocking you, but it is a real config inconsistency and we want to fix it properly given the attached volume. We are looking into correcting it on our side without touching your volume or data, and will follow up here.

Status changed to Awaiting User Response Railway • 30 days ago

Status changed to Awaiting Railway Response sam-a • 30 days ago

sam-a

EMPLOYEE

a month ago

Following up on the region warning: good news, there is nothing actually wrong with your service's configuration, and please do not change the region.

We dug into it on our side. Your service is configured for our US West (sfo) region, and your volume is placed in that same region, so compute and data are correctly colocated. Deploys are working (your latest went live at 19:09 UTC), which confirms the platform is happy with the config.

The "Invalid region sfo" warning is a bug in the settings UI: it validates the configured region against a list that uses our older long-form region names, and does not recognize the newer short identifier your service uses. The warning is cosmetic and is not blocking anything. We have flagged it to the team to fix the validation, and I would specifically advise against using any region replacement option if one appears, since your volume lives in that region.

Sorry for the confusion the warning caused on top of the queue incident. If deploys ever do get stuck again, reply here.

Status changed to Awaiting User Response Railway • 30 days ago

Railway

BOT

23 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 • 23 days ago

Welcome!