Status and time in QUEUED
Anonymous
FREEOP

a month ago

Deployments for the goosto-staging service remain in a QUEUED/Processing deployment state for over 20 minutes. The integration with the GitHub repository was disconnected and reconnected, but the issue persists. Branch: staging. Commit: 4b8ebd0674d53291b5bda070df7f48bbb3efddae.

My workspace subscription is active under the Limited Trial plan. It has $2.89 in credits and 11 days remaining. GitHub is connected correctly. Therefore, this is not an inactive subscription or insufficient credits issue.

Solved

3 Replies

Railway
BOT

a month ago

Your workspace is currently showing as INACTIVE, which is preventing deployments from processing. You have $2.89 in remaining trial credit and 11 days left, so this state does not reflect expected usage. Try logging out and back in, then check if the workspace state has recovered at your workspace billing page. If it still shows inactive after that, reply here and we can dig further.


Status changed to Awaiting User Response Railway about 1 month ago


Anonymous
FREEOP

a month ago

I logged out completely, closed all Railway tabs, logged back in, and checked both the Plans and Billing pages.

The dashboard still shows:

  • Active Plan: Limited Trial
  • $2.88 in remaining credits
  • 11 days remaining

However, deployments are still not processing. The dashboard shows an active trial, while Railway's internal workspace state is reported as INACTIVE.

Please restore or resynchronize the workspace's internal active status. I have attached screenshots of the Plans and Billing pages.

Captura de tela_21-7-2026_164954_railway.com.jpeg

Captura de tela_21-7-2026_164947_railway.com.jpeg


Status changed to Awaiting Railway Response Railway about 1 month ago


sam-a
EMPLOYEE

a month ago

You were right that this wasn't a subscription or credits issue. Deploys on trial workspaces were temporarily queued during an upstream GitHub incident earlier today, and the internal "INACTIVE" state mentioned earlier is just how trials are represented in our system, not a problem with your account.

The queue has since drained and your goosto-staging deployment completed successfully at 23:24 UTC. Apologies for the runaround.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved sam-a about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...