im having a really weird issue i cant solve. i deploy a service (basic discord bot) and the deployment logs show the deploy>pre-deploy command getting hung up. there is no manually created pre-deploy command.

i have tried everything i can think of. just trying to store a single persistent json file in the volume. created logs that do indeed confirm the file is being created and accessible by my bot so i dont think its a path issue. The bot service will deploy just fine and will run perfectly fine but the deployment logs still after 15 hours show a circle spinning at the step i defined above.

i tried many variations of code tweaks and also many variations of manually putting in a pre-deploy command. this caused the deployment check to pass in the logs but then the post-deploy check wouldnt even start.

i earlier tried removing the volume and re-deploying and this fixed that issue and got clear all the way through the post deployment check, everything all green. so the issue seems isolated to the volume being attached. i have tried wiping the volume, deleting it and recreating it, seems if a volume is attached to that service in anyway this issue occurs.

the bot is purely python, used a dockerfile in the repo to deploy. so tried just deleting that and letting nixpack do its thing thinking might be some root issue. still didnt fix this. created a new variable as per the docs with RAILWAY_RUN_UID and the value set to 0. still nothing. tried every variation of all these things in combination and also spent endless hours tweaking the code...still same issue.

but alas the bot is running and seems to work fine hahaha. sooooo any advice please?