3 hours ago
Hello Railway Support,
The attached orphan Redis service cannot be deleted because its TCP proxy deletion is stuck in the Railway backend.
The affected service has no deployment and no volume, and it is safe to delete.
Current symptoms:
- The dashboard shows the TCP proxy for application port 6379 permanently as "Deleting".
- railway tcp-proxy list --json returns an empty proxy list.
- Checking the previous proxy reports that it is not found.
- Deleting the service fails with: "Cannot delete TCP proxies: an operation is already in progress".
- The same failure occurs in Railway CLI v5.26.1 and in the dashboard.
- Railway Agent inspected the service configuration and found networking.tcpProxies still contains an entry for port 6379, consistent with a stale backend operation lock.
Requested action:
- Verify that the stale proxy is absent from the network layer.
- Clear the stuck TCP proxy operation/configuration lock.
- Delete the attached orphan service, or confirm when it is unlocked so I can delete it.
Important: there is another healthy Redis service with a persistent production volume in this project. Please do not modify that active Redis service.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
2 hours ago
The stuck TCP proxy is cleared. A delete operation for that proxy started back in March but never finished, which left the service locked with "an operation is already in progress." We ran a repair on the backend to complete the deletion, and the proxy is now fully removed from the network layer.
You can delete the Redis-Kd9x service yourself now. Your other Redis service and its volume weren't touched.
Railway Team
Status changed to Awaiting User Response Railway • about 2 hours ago