Configuration changes made via the API, including volume removal, are staged and not applied immediately. After your mutation stages the change, you need to call the environmentPatchCommitStaged mutation to actually commit and deploy it. Without that step the change is only queued, not executed. You can verify pending staged changes with the environmentStagedChanges query, and the staged changes docs cover the full flow.

how do i "call a mutation" ?

Call this GraphQL query to call the mutation, pass your environment id as a variable environmentId (This need to be ID of the environment the changes are staged)

mutation environmentPatchCommitStaged($environmentId: String!) {
environmentPatchCommitStaged(environmentId: $environmentId)
}

There also cURL, Javascript, Python example on the docs:

https://docs.railway.com/integrations/api/manage-environments#commit-staged-changes

i ran this command but the volume is still there, is there something in the UI i can do to just remove the volume?

How your project UI looks right now? If you have remove the volume through the volume settings or the API, you will see a notification says "1 Staged Changes" followed by Discard and Apply Button, Applying it will commit the changes and your volume will be deleted completely

there's only wipe volume and delete volume, i cloned a production app to a staging app and i want to use a different volume for that

is there anyway i can get support to look at my account? its looking super wacky and the agent is even saying the same

Wipe Volume will clean the volume data, Delete volume will remove the volume from the project environment

I cloned a production app to a staging app and I want to use a different volume for that

You mean cloned the production environment to staging environment? If so, then you will have 2 different volumes, and staging volume won't affect the production one