Skip to content
Wait for CI stuck after successful workflow runs following Free-plan reactivation
yousramahrospro-a11y
OP

6 days ago

Our service remains unavailable after the trial expired and we reactivated the workspace on the Free plan. We need help with Railway's Wait for CI gate, while keeping it enabled.

What we checked on 13 November 2026:

  • The Railway GitHub App is installed, can access the connected repository, and already has actions, checks, commit statuses and workflows permissions. There are no pending Railway permission updates.
  • The connected branch is correct and the workflow runs on push.
  • The full workflow passed. We reran it and it passed again.
  • A new documentation commit triggered a fresh deployment and a fresh full workflow. Both jobs passed, including production startup and a Linux container/persistent-volume test. GitHub reported the whole workflow completed/success at 17:42:04 UTC.
  • Railway still shows WAITING FOR CI after a dashboard reload. The service's health endpoint returns 404.
  • Known external-contributor commits were approved through the normal deployment prompt. We have not disabled Wait for CI or modified check results.
  • Other GitHub app check suites (Netlify and Claude) remain queued. The Railway documentation says these are ignored. We have not cancelled them.

Is there a supported way to refresh or re-evaluate the GitHub completion event without bypassing Wait for CI? We want to preserve the existing persistent volume and remain on the Free plan during testing.

Project and deployment identifiers can be supplied to Railway staff through an appropriate channel if needed.

Awaiting User Response

1 Reply

Railway
BOT

6 days ago

With Wait for CI enabled, a deployment stays in WAITING until every GitHub Actions workflow run on that exact commit has finished, and it looks at each workflow run's conclusion rather than individual jobs. Checks from other GitHub apps, such as the queued Netlify and Claude suites, are ignored. A failed workflow skips the deployment, and if the workflows on that commit have not all finished within two hours, the deployment is skipped rather than left waiting.

To trigger a fresh deployment of the connected branch without turning Wait for CI off, open the Command Palette (Ctrl+K, or Cmd+K on Mac) and select Deploy Latest Commit. This starts a new deployment from source and does not change your volume or your plan.

So we can match the stuck deployment to its GitHub run, please share the commit SHA of the documentation commit that is still showing WAITING FOR CI and the UTC time it was pushed.


Status changed to Awaiting User Response Railway • 6 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...