This has been fixed.

This deployment failure is on our side, not yours. The error in the SNAPSHOT_CODE step originates from our internal deployment pipeline, not from your application code. Your service and project are intact, and because this service has no persistent volume attached, no stored data is at risk.

im still having this issue

Could you clarify what issue you're having specifically? The original issue in this thread has been resolved.

Deploys have been failing since the morning. It dies at Initialization >

Snapshot code, before the build even starts:

Invalid prisma.workspace.findMany() invocation:

The column Workspace.supportTierOverride does not exist in the current database.

My service is Python/FastAPI. No Node, no Prisma, and there's no Workspace

table in my database, so this looks like it's coming from your side rather

than my app.

I've redeployed a few times, same result each time.

That error is left over from a bug that was deployed on our end this morning, and Redeploy is what's keeping it alive. Redeploy reuses the failed attempt's config, which never got your start command, so it fails again and shows the old message. Press Cmd+K in the project, pick "Deploy Latest Commit", or push a new commit. That runs a fresh deploy from your repo and picks up your railway config file again. Your Postgres data isn't affected.