Repository snapshot timed out when deploying private repo
adnexa91
FREEOP

3 months ago

Hi everyone,

>

> I’m having a persistent issue when deploying my backend service on Railway.

>

> Project: perpetual-fulfillment / bubbleflow2-backend / production

> Service: bubbleflow2-backend

> Region: europe-west4

> Repository: AdNexa91/bubbleflow2-backend (private GitHub repo)

>

> Every deployment fails during the Initialization › Snapshot code step, before the build starts. The error message is:

>

> Repository snapshot operation timed out. This may be due to a large repository size or network issues. Please try again in a few minutes.

>

> Earlier today I also saw:

> We failed to clone your repository, likely due to a network issue. Please try again in a few minutes.

>

> What I already checked:

> - The Railway GitHub App has access to All repositories in my GitHub account.

> - The service is linked to AdNexa91/bubbleflow2-backend on the master branch.

> - The repository is accessible from my side (I can clone and pull it locally without issues).

> - I tried: disconnecting/reconnecting GitHub, creating a new service from the same repo, changing regions, and redeploying multiple times.

>

> The snapshot step always times out and the build never starts.

>

> Questions:

> 1. Is there any known issue that could cause repository snapshot timeouts for private repos?

> 2. Does my repository size exceed a limit for the snapshot step, and if so, what is the recommended workaround (e.g. backend-only repo)?

> 3. Could someone check the logs for my project/service and let me know what is blocking the snapshot operation?

>

> Thanks a lot for your help!

>

> Best,

Solved

2 Replies

Railway
BOT

3 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


3 months ago

Howdy!
That would align with a current GitHub outage. Because of it, repos can be stuck in a "Snapshotting" state. You can view their incident here https://www.githubstatus.com/incidents/5q7nmlxz30sk.


Status changed to Awaiting User Response Railway 3 months ago


Status changed to Solved adnexa91 3 months ago


Loading...