Hey team — running into a Railway-side sync issue that I've fully exhausted from the user side. Hoping someone can force-refresh my account from the backend.

Problem: The repo confident-ai/confident-cloud doesn't appear in Railway's repo picker for my account, and the confident-backend service shows "GitHub Repo not found" on the branch field. My coworker on the same project sees the repo and can change branches without issue.

IDs:

GitHub username: yekta-ko

Org: confident-ai

Repo: confident-cloud

Project ID: 22fb7f66-ed07-448b-9b9b-a6d7aaff2321

Service ID: 8f6bd49c-7e75-411b-8363-f75cf0fff67d

Environment: monorepo-staging

Context: I accepted a GitHub invitation to the repo today. I'm a confirmed member of the confident-ai org (verified at github.com/settings/organizations). The Railway GitHub App is installed at the org level with confident-cloud explicitly in the allowed repo list — confirmed by screenshot showing "installed" status.

What I've tried (all from the user side):

Confirmed org membership (not just repo collaborator)

Verified org-level Railway GitHub App install includes confident-cloud

Installed Railway GitHub App on personal GitHub account with "All repositories" (since removed)

Full Railway logout and re-login via GitHub

Account-level GitHub disconnect/reconnect from Railway integrations page

Service-level repo disconnect/reconnect

Hard refresh of Railway dashboard

Interesting detail: The repo partially resolves — when I open the source repo settings on the service, the root directory listing works (I can see frontend/, backend/, etc., which are subdirs of confident-cloud). But the branch lookup fails, and confident-cloud doesn't appear in the repo picker dropdown when I try to reconnect. The other confident-ai repos do appear in the dropdown.

This looks like a stale per-user repo cache on Railway's backend that wasn't invalidated when my GitHub access changed. Can someone force-sync my account's accessible repos?