I’m running into an issue where Railway CLI commands that depend on project linkage consistently fail with:

Problem processing request

Authentication and basic project access appear to be working correctly.

These commands work:

railway whoami

railway list

railway list --json

railway list --json successfully returns the project, production environment, and all services. The environment also reports:

"canAccess": true

However:

railway status

returns:

Problem processing request

I tried removing the local link and recreating it:

railway unlink

railway link

The interactive flow successfully lets me select:

Workspace

Project

Production environment

Immediately after selecting the environment, it fails with:

Problem processing request

I also tried linking non-interactively using the project and environment UUIDs:

railway link \

--project <PROJECT_ID> \

--environment <ENVIRONMENT_ID>

This fails in the same way.

I originally reproduced this on Railway CLI 5.49.6. I then installed 5.52.1 using Railway’s direct installer and got exactly the same behaviour, so it does not appear to be specific to the older CLI version.

The CLI can therefore:

authenticate successfully

enumerate the workspace/project

retrieve the environment

retrieve all project services

confirm that I have access to the environment

but it cannot establish the project/environment link.

Has anyone seen this before? It feels like there may be some inconsistent project/environment metadata or backend state that railway link / railway status is encountering.

Is there any debug logging or another command I can run that would expose the underlying API error rather than the generic Problem processing request message?