deployment queued due to upstream github
bhizzo
FREEOP

a month ago

i can proceed with my deployment +20 minutes now nothing

Solved

3 Replies

Railway
BOT

a month ago

Your most recent deployments all show as completed successfully. If you had "Wait for CI" enabled in your service settings, deployments will stay in a WAITING state until your GitHub Actions workflows finish, which can cause delays. You can check this under your service's Settings tab. If the issue has since resolved on its own, no further action is needed.


Status changed to Awaiting User Response Railway 30 days ago


bhizzo
FREEOP

a month ago

nothing is completed still show queued and i see alot are facing the same problem whats the issue? i tried deleting the service and adding a new one still the same issue


Status changed to Awaiting Railway Response Railway 30 days ago


Railway
BOT

a month ago

Your account is currently on the Trial plan, which is subject to deployment queuing during peak hours. Your service deploys to US West (SFO), where peak hours are 8 AM to 8 PM PT, and you're within that window right now. During these periods, deployments for free and trial-tier users may be queued while platform resources are prioritized for paid-tier users. You can either wait until after 8 PM PT to deploy, or upgrade to the Hobby plan to remove this restriction entirely.


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!

Sign in to your Railway account to join the conversation.

Loading...