Skip to content
Deploy Latest Commit fails with “Deploys have been paused temporarily” after build incident resolved
imaninaramly
OP

a month ago

Title

Deploy Latest Commit fails with “Deploys have been paused temporarily” after build incident resolved

Body

I am trying to deploy recent updates to my Build With Us website. I expected Railway to build the latest commit from the connected GitHub branch, but the new commits have not become active, and a manual “Deploy Latest Commit” attempt failed with a temporary deploy pause message. The existing website is still online, but it is running an older version, so the recent editor fixes are not available. Please check why this service still cannot trigger a new deployment and help restore deployment of the latest commit.

Affected resources: Railway project proud-upliftment, environment production, service buildwithus.my, domain www.buildwithus.my. Connected repository: https://github.com/imaninaramly/buildwithus.my.git, branch main. The latest pushed commit is 95505dd (“Refresh editor assets and number visible pages before display”), committed on 21 October 2026 at 10:37:15 MYT (UTC+08:00). The workspace ID and deployment IDs are not available from the screenshots.

Observed state and timing: A Railway dashboard screenshot saved on 21 October 2026 at 10:39:58 MYT showed the service as Online, a “Limited Access” banner, and an active, successful deployment titled “Simplify Pixel Game card and editor heading” (commit d0442ce, committed at 10:12:57 MYT). The dashboard displayed that active deployment as approximately 25 minutes old. This is the currently running deployment, not a failed deployment of 95505dd. The same screenshot showed a toast saying:

Failed to trigger deployment
Deploys have been paused temporarily

The user subsequently reported the same “failed to trigger deployment” result after trying the suggested manual deployment. The exact time of that retry and any deployment ID were not captured. The last observed state is therefore an online older deployment with new deployment triggers failing.

Checks and attempts: Commits 46e5e27, 57d6297, and 95505dd were pushed to main; the latest local tests passed before 95505dd was pushed. The service dashboard still showed the older active version. The assistant then suggested Railway’s Command Palette → “Deploy Latest Commit”; the user reported that this also failed. There is no evidence that a new build started or that the latest commit reached production. No DNS or service configuration changes were made as part of this troubleshooting.

Railway’s incident page, https://status.railway.com/incident/JUA1PC5H, reports the build pause as resolved and says deploys triggered during the pause must be triggered again. The later dashboard screenshot still showed “Limited Access,” so the current reason for this service’s rejection is uncertain. Please inspect the service’s deployment trigger state and any workspace or platform restriction, explain the rejection, and advise how to deploy commit 95505dd while preserving the currently running service and attached volume.

The AI assistant first suggested contacting Railway support after the user reported that the manual deployment trigger still failed, because the public incident was marked resolved but the Railway dashboard continued to reject this service’s deployment. The assistant does not have access to this Railway workspace to inspect its internal deployment state.

Prepared with Railway's support template (v1).

Solved

3 Replies

Railway
BOT

a month ago

We're sorry for the trouble. The earlier build incident you linked is resolved, but we have since paused builds again for Free, Trial and Hobby workspaces, which is why triggering a new deploy on your Hobby workspace is being rejected with that message and why the "Limited Access" banner is showing. We're working on it, and you can follow updates at status.railway.com/incident/PX5UYXCN.

Your currently running deployment and its volume are not affected, since services that are already running keep serving traffic while builds are paused. Nothing on your account is restricted, so once builds resume for Hobby workspaces, use Deploy Latest Commit again to build commit 95505dd.


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


imaninaramly
OP

a month ago

why it happened again?


Status changed to Awaiting Railway Response Railway • 30 days 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 • 30 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...