Service stuck in deletion for 24+ hours - Cannot deploy due to corrupted cache
tecautec
FREEOP

8 months ago

Hello Railway Support Team,

I'm experiencing a critical issue with my project deployment:

Problem Description:

- Service was deleted 24+ hours ago but still appears in dashboard

- Service shows "Service will be deleted" status but never completes deletion

- Unable to create new deployments due to corrupted nixpacks cache

Error Details:

- Error: "Failed to parse Nixpacks config file nixpacks.toml"

- "invalid type: map, expected a sequence for key providers at line 7 column 1"

- This error persists even after creating valid nixpacks.toml files

Actions Attempted:

1. Deleted and recreated nixpacks.toml multiple times

2. Added environment variables: NODE_VERSION=20, NIXPACKS_NODE_VERSION=20

3. Modified railway.json with correct Node.js version settings

4. Made multiple commits to force cache refresh

5. Attempted service deletion (stuck for 24+ hours)

Project Details:

- Repository: tecautec/vendeflex

- Framework: Node.js/Express with React frontend

- Issue: Railway cache seems corrupted and ignores all configuration changes

Request:

Please manually delete the stuck service and clear any cached configurations so I can redeploy the project cleanly.

GitHub Repository: https://github.com/tecautec/vendeflex

Project URL:

Thank you for your assistance.

Regards,

Leo Moura

CEO and Dev in Tecautec

Phone Number: 55 85 98159 9296

Email: tecautec@gmail.com and contato@tecautec.com

Solved

2 Replies

Railway
BOT

8 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


8 months ago

I see no service in that project?


Status changed to Awaiting User Response Railway 8 months ago


Railway
BOT

7 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 7 months ago


Loading...