Disabling the PR environments toggle only prevents new ones from being created, it does not clean up existing ones. PR environments are normally auto-deleted when the associated PR is merged or closed, so if you have 22 lingering, the corresponding PRs on GitHub may still be open. You can delete them yourself from Project Settings > Environments in the dashboard, or via CLI with railway environment delete <name>.

how can i be sure that i am not deleting any important production environments when i delete pr environments though?

PR environments are named after their associated Git branch (e.g. feature/my-change) while your persistent environments have names like production or staging, so they are easy to tell apart in the environment list under Project Settings > Environments. Your production environment is the default one created with the project and will not show a branch-linked name.

What would be preferred here is : only spin up PR environments on NON-DRAFT PRs with a specific label (e.g. Ready-to-merge). Railway are you listening ? (not the railway bot, actual product ppl)

That filtering isn't available today. PR environments are either on or off per project, with an additional toggle for bot-authored PRs and a "Focused PR Environments" option that limits deploys to services affected by the changed files. There's no way to filter by draft status or label.

You can post this as a feature request on our roadmap at https://station.railway.com/roadmap so other users can upvote it and the product team can track demand.