Experiencing a broken GitHub source binding on my worker service that prevents

any new deployments. The service continues running on the previous deployment

but cannot be updated. Looking for help refreshing the backend binding or

guidance on alternative paths.

Project details:

- Project: prolific-abundance

- Project ID: 0b8fd38c-2425-4133-b89d-77034dcd5657

- Service: worker

- Service ID: abab1cf1-3848-4a10-9a48-d9d05112be57

- Environment: production (b47c0ff9-9c6a-42f7-ad7d-808045b922c9)

- URL: https://worker-production-046b.up.railway.app

- Volume: worker-volume mounted at /app/data (321 MB / 500 MB - critical,

must be preserved)

- Current deployment_id: 09bce647-1eb6-40e0-8bc3-873d329ea2ed (SUCCESS, running)

Repository:

- Current: ncorrochano/Trading-Bot (private, capital B)

- Previous (before rename): ncorrochano/Trading-bot (lowercase b)

Sequence of events:

1. ~3 weeks ago: I renamed the repository on GitHub from 'Trading-bot' to

'Trading-Bot'.

2. After the rename: The Source section still displayed 'ncorrochano/Trading-Bot'

as connected, but new commits to main stopped triggering builds.

railway redeploy --from-source -y began returning 'Not Found'.

3. Today: Attempted Disconnect+Reconnect via Settings UI. The "Apply 2 changes"

staged modal repeatedly showed Branch: main->main and

Repo: ncorrochano/Trading-Bot->ncorrochano/Trading-Bot (identical

before/after values), with the error 'An unknown error occurred'

preventing the changes from applying.

4. Following Railway docs suggesting GitHub App reinstall, I uninstalled

the Railway App from my GitHub account. After this, the Source section

shows 'GitHub Repo not found' / 'No GitHub installation found for repo:

ncorrochano/Trading-Bot'.

5. Reinstalling the Railway App via GitHub fails with persistent 404 on

https://github.com/apps/railway-app/installations/new/permissions?target_id=274930260.

This 404 occurs in normal browser, InPrivate/Incognito with fresh login,

and when triggered from Railway's "Configure GitHub App" button.

Reported separately to GitHub Support.

Asking:

(a) Refresh the backend binding cache for service worker

abab1cf1-3848-4a10-9a48-d9d05112be57) so that, once GitHub Support

resolves the 404 and I can reinstall the Railway App, the existing

service automatically picks up the fresh installation.

(b) Guidance on migrating this service to a new source connection while

preserving the volume worker-volume at /app/data (Tiingo SQLite

cache + persistent state.json critical to the application).

(c) Any alternative path you'd recommend.

Workaround attempted (failed):

railway up --detach from a local clone. CLI 4.57.1, Git Bash MINGW64,

Windows 11. Created .railwayignore reducing upload from 164 MB to 1.4 MB.

CLI succeeded at "Indexed" and "Compressed 100%" but failed at upload with

'Access is denied. (os error 5)'. Suspect Windows Defender or Cisco AnyConnect

VPN blocking. Could not isolate.

What works:

- railway login: OK

- railway link: OK

- railway status: returns correct info

- railway redeploy -y (without --from-source): SUCCESSFULLY redeploys

existing image

- railway logs --deployment, railway logs --build: working

What fails:

- railway redeploy --from-source -y: returns 'Not Found'

- railway up --detach: 'Access is denied. (os error 5)' at upload phase

Context:

The Railway Lovable guide explicitly states 'GitHub sync breaks if the

repository is renamed, moved, or deleted'. I'd prefer not to rename back

to lowercase as it would create cascading cleanup. The bot is paper trading

(no real funds at risk), but it's a real production workload I rely on.

Thank you for any guidance.