Hi team — I'm on the Hobby plan and hit what looks like an account-level

credential cache issue after renaming my GitHub account.

## What happened

I renamed my GitHub account: silverwebgroup → wladyslawkulik.

Since then, deploys are broken across the whole workspace — not just one

project. It's clearly an account-level state issue on Railway's side,

not a per-repo problem.

## Symptoms

1. All 5 existing services show "Bad credentials" under

Branch connected to production.

2. Creating a brand new project from a repo also fails:

attempting to create a project from wladyslawkulik/goodysell-countdown-timer

returns "Failed to fetch repository files".

(Screenshot: [attach])

3. The deploy that eventually went through on one service built from

the OLD repository path — deployment history shows

"Merge pull request #53 from silverwebgroup/chore/update-faq"

even though the Source Settings UI shows the new

wladyslawkulik/goodysell-countdown-timer URL.

This suggests Railway is still resolving the repo via GitHub's

rename redirect internally.

## What I've already tried (all from my side)

- Disconnected and reconnected the repo on every service

- Revoked Railway OAuth authorization and reinstalled the GitHub App

from scratch

- Logged out and back into Railway

- Created a brand new service — same "Bad credentials" error

- Verified the GitHub App installation shows all repos under the new

username with full permissions granted

## Why I think it's a backend cache

The GitHub App integration works for listing repos — the repo picker

shows wladyslawkulik/... correctly for all my repos. But the

credential used for actual git fetch / clone still fails. That points to

two separate tokens on your side, and the fetch one is pinned to the old

username. A standard disconnect/reconnect from the UI doesn't clear it.

## Details

- Project ID: 2fd19766-e2f0-46cc-83d9-d3960bfe5175

- Service ID (newly created, still failing): 97106ae2-d04f-44da-9110-9f0cfd1f2f64

- Old GitHub username: silverwebgroup

- New GitHub username: wladyslawkulik

Happy to provide additional IDs, logs, or run any diagnostics. Would it

be possible to force-reset the cached token on the account so the new

username is picked up?

Thanks!