973d1d4e-0626-47c2-96bf-d8f299dff64b

Seems to be specific to this project

Hey, have you tried redeploying the affected services? You can try deploying the latest commit using CMD/CTRL + K.

Yes 11 times in the last 52 mins

https://railway.com/project/973d1d4e-0626-47c2-96bf-d8f299dff64b/service/5408368f-666b-4cb8-a6c8-f7a1bf8f1708?groupId=6e585a96-f33a-482d-817b-417a7dd8eb42&environmentId=6fe8dd01-0a88-464f-8dc2-e78d140cbd34

Both environments staging / production have the issue on trying to clone different branches.

I'll raise this thread to the team for further assistance.

!t

Thanks, not sure if you can merge it, but opened an issue on Slack as well: http://go/slack-ext/aWQ9dGhyXzAxazViZjc4OTFlbjl0YWNweGFlM3EzYjZo

I personally don't have access to Slack, however you should receive support from the team faster on Slack than on Discord.

Well you are the first who responded 😄

Anyway to get this bumped? The service is now undeployable for many hours.

Things we tried:

• Reconnecting the repo does not work.
• Spinning a new service with this repo does not work.
• Create new repo and connect it does not work.

any screenshot, maybe i can try to help on this?

also any chance you revoked railway's permission on github repo?

Error shown on the builds

No permissions were changed

Let me try to reproduce on my side <:Fingers:1202140286956867644>

Thanks, I've double checked the permissions. Also I can search and find the repo fine on creating a new service.

Interesting, I tried from all four regions, but it's cloning properly 🤔

i'll leave it to the team, as i dont have access to the project

Thanks for checking

Really seems an issue on Railway side. I've moved the cloning into a dockerfile which works fine.

Hey, I'm going to close this thread in favor of your thread on Slack. Going forward, please avoid opening duplicate threads.