Hi Railway team,

I'm hitting two simultaneous blockers that prevent deploying new code to my project.

Environment

• Project: abundant-flow (id: 232258e7-dc82-4c7f-b73a-926563fbdefb)
• - Environment: tempoflow-mvp (id: 02816d7a-4100-49fe-95e7-da6c27cd9853)
• - Service: tempoflow-api (id: 6aeb5989-e733-464d-8499-83d780a3b64c)
• - Plan: Hobby
• - Railway CLI: v4.40.0

Issue 1 — railway up --ci upload keeps timing out

Repeated attempts all fail identically:

Indexing... 
Compressed [====================] 100%
Failed
error sending request for url (https://backboard.railway.com/project/232258e7-.../environment/02816d7a-.../up?serviceId=6aeb5989-...)
Caused by:
    operation timed out

Context:

• Tarball size is tiny (~628 KB, measured locally with same excludes as .dockerignore)
• GET requests to Railway API work fine (200 in ~200ms, status page OK)
• Tried from 2 network connections, same result
• First occurrences this morning, still failing now (~12h)

Issue 2 — Service > Settings > "Connect Repo" picker returns "No repositories found" for every search

The Railway App GitHub integration is correctly configured:

• GitHub App installed on account laurentducatel-ctrl
• Permissions granted to laurentducatel-ctrl/tempoflow-mvp (verified in https://github.com/settings/installations)
• Tried typing full name, partial name, clearing search, clicking Refresh — picker stays empty
• Same behaviour in both production and tempoflow-mvp environments

As a result I cannot use the upload path (timeout) nor switch to GitHub-auto-deploy.

What I need

Either:

1. Root-cause the upload timeout on this project, OR
2. Help resurface the repo picker so I can connect laurentducatel-ctrl/tempoflow-mvp to the service and use GitHub-triggered redeploys.

Latest code is already pushed on GitHub main: https://github.com/laurentducatel-ctrl/tempoflow-mvp (commit 157bd91). Build has worked in the past — successful deploys earlier today via the same railway up flow.

Thanks!