12 hours ago
My Railway service wantedstuff is running an older ACTIVE deployment, but three newer deployments remain stuck in QUEUED status.
The queued deployments include fixes for production login and logout redirects. Their build and deployment processes have not started.
My website, https://wantedstuff.com, remains online, but I cannot deploy these important corrections.
Railway is also displaying the recovery notice for the October 21 incident.
Could you investigate why these deployments are queued and help restore normal deployment processing?
1 Replies
Status changed to Awaiting Railway Response Railway • about 12 hours ago
3 hours ago
Your queued deployments started processing at 06:45 UTC. The deployment for the wantedstuff service that serves your custom domain, and the one for wantedstuff-daily-jobs, have both completed successfully, so the login and logout redirect fixes are now live there.
The third deployment, for the separate wantedstuff service in your other project, failed during the build. Its build logs show npm run build exiting because the Prisma config file could not resolve the DATABASE_URL environment variable, so that service needs DATABASE_URL available in its variables before it can build.
Status changed to Awaiting User Response Railway • about 3 hours ago