Skip to content
Source update applied but no new deployment appears
jinhan0830-eng
OP

a month ago

On a Trial workspace, a source-code update was accepted and Activity shows a change applied, but the deployment list still shows only the previous successful deployment. There are no visible pending changes or queued/building deployments. A Limited Access notice appeared earlier.

How can I determine whether the deployment trigger failed or is still pending internally, and what is the supported way to resume without creating duplicate deployments? Please clarify whether an explicit redeploy is needed after Limited Access ends.

Solved

5 Replies

Railway
BOT

a month ago

Your change was saved, but the deployment it tried to start at 02:22 UTC today was rejected. At that time we had temporarily paused deploys for Free, Trial and Hobby workspaces, and the Limited Access notice you saw came from that pause. That incident is now resolved: status.railway.com/incident/PX5UYXCN.

The rejected deploy failed outright. It was not queued, so nothing is still pending and nothing will start later on its own. That is why your deployment list only shows the previous successful deployment.

Yes, you need to deploy again yourself now that the pause is over. Because nothing is waiting in the background, a single new deploy will not create a duplicate. One way to deploy from your latest source is to press Ctrl+K (Cmd+K on Mac) to open the command palette and select Deploy latest commit.


Status changed to Awaiting User Response Railway • about 1 month ago


jinhan0830-eng
OP

a month ago

Could a human Railway team member please clarify the automated answer? It says the deployment was rejected and was not queued, while the cited incident notice says new deployments would stay queued until builds resumed.

This is a request for clarification, not a report of a new outage. With a source change shown as applied but no new deployment record, which supported check definitively distinguishes a missing deployment trigger from a pending internal workflow? Once that check confirms nothing is pending, what is the supported way to resume safely without creating a duplicate deployment?


Status changed to Awaiting Railway Response Railway • about 1 month ago


jinhan0830-eng
OP

a month ago

One additional technical detail: this is a Railway Function/source-code service, and the command palette offers "Redeploy source image".

Does that action deploy the currently applied Function source/start command, or reuse the previous deployment's configuration snapshot? What is the official UI equivalent of the documented serviceInstanceDeployV2 API for deploying the current service configuration? I would like to confirm the correct action before resuming, to avoid deploying stale configuration or creating a duplicate.


Status changed to Awaiting Railway Response Railway • about 1 month ago


jinhan0830-eng
OP

a month ago

Update: the earlier redeploy succeeded. A subsequent source update returned "16 UNAUTHENTICATED" during staging, and no new deployment was created. Existing read-only queries still succeed.

When reconnecting through the existing connected-account settings, the user sees "Error authenticating with GitHub" and "Problem completing OAuth login".

Could a human Railway team member help distinguish an authentication/login handoff problem from a write-tool authentication failure, and provide a supported recovery path that preserves the existing connection without disconnecting or deleting it?


Status changed to Awaiting Railway Response Railway • about 1 month ago


chandrika
EMPLOYEE

a month ago

We're investigating platform-wide degradations and will share more when we have more details


Status changed to Awaiting User Response Railway • about 1 month 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...