GitHub source snapshot fails before build
bondarsvetlana096-cyber
HOBBYOP

40 minutes ago

Hello,

My production service can no longer complete the GitHub source snapshot.

GitHub-connected deployments repeatedly fail at:

Initialization → Snapshot code

On one attempt Railway reported:

GitHub rejected the credentials Railway used to read the repository. The Railway GitHub App's access to this repository is no longer valid.

A subsequent manual Deploy latest commit attempt remained in Initialization for approximately 55 minutes and then failed with:

snapshot operation was canceled

Neither attempt reached Docker build, container creation, or application startup.

The previous production deployment remains healthy and serving normally. Railway can still display the connected repository, branch and commit metadata, but cannot complete the source snapshot.

I have stopped retrying deployments.

The repository currently contains approximately 6.92 GB of tracked files, mostly static image assets, with approximately 6.91 GB under the backend directory.

Could someone from Railway please clarify:

Whether this error indicates that the Railway GitHub App authorization needs to be repaired.

Whether there is a safe way to refresh the GitHub source authorization without disrupting the currently healthy deployment.

Whether a repository of approximately 6.9 GB is supported by Railway's GitHub source snapshot pipeline.

Whether there is a source snapshot size or timeout limit that could explain the repeated approximately 55-minute cancellation.

I have deliberately not disconnected/reconnected the repository because the existing production deployment is healthy.

Thank you.

$10 Bounty

1 Replies

Railway
BOT

34 minutes ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 34 minutes ago


Have you tried deleting the Railway github app from https://github.com/settings/installations, and installing it again? Relinking the github repo might also help (it won't affect the previous healthy deployment if it fails).


Welcome!

Sign in to your Railway account to join the conversation.

Loading...