I am unable to deploy my service from GitHub. All deployments get stuck on “Initializing” and then fail without producing any meaningful build logs.

Repo: craigcbutterworth-png/pitchpulse

Branch: main

Root directory: /backend

The only message shown in the build logs is:

“Railway can’t access craigcbutterworth-png/pitchpulse. Reconnect the GitHub repository under Service Settings → Source, or reinstall the Railway GitHub App and grant it access to this repo.”

What I’ve already tried

• Reinstalled the Railway GitHub App
• Granted access to all repositories (including pitchpulse)
• Confirmed the repo exists and is accessible in GitHub
• Disconnected and reconnected the repo under Service Settings → Source
• Revoked and re-authorised Railway in GitHub (both Installed App and OAuth Apps)
• Reconnected my GitHub account within Railway
• Confirmed there are no remaining “No project member has access” warnings
• Tried creating a completely new Railway project and reconnecting the repo
• Confirmed billing is active (not a trial/credit limitation)
• Verified backend structure is valid (/backend contains package.json and server.js)

Behaviour

• Deployment starts
• Stuck on “Initializing”
• Fails without progressing to build
• No logs beyond the repo access message
• Diagnosis also fails

Expected behaviour

Railway should be able to access the GitHub repository, initialise the deployment, and proceed to the build stage.

Request

Please can you check whether the GitHub integration/token or repository access state for my workspace/service is stuck or corrupted on Railway’s side?

Given the steps already taken, this appears to be a Railway-side issue rather than a configuration issue within my project.