Hello, my Supabase template recently began experiencing issues during deployment. In Supabase, every service depends on the Postgres service building first and virtually all of them do reference Postgres.RAILWAY_PRIVATE_DOMAIN in their ENV configuration. They need Postgres to be up and running so they can execute migrations on first startup. However, 4 of the services are building and deploying before Postgres is finished building. I'd like to understand why, and fix this issue.

For what it's worth, my suspicion is that sometimes, when chains of dependency via Shared Variable reference are in conflict (that is, it's technically impossible to honor ever dependency chain because it would create a deadlock), the orchestration engine picks one dependency chain and ignores the others. I really need to have a specific dependency chain among services honored and followed every time.

Project ID: cd22524a-2d8b-4ec7-8ea5-bedb4df89632

Template listing: https://railway.com/deploy/complete-supabase-nextjs-frontend

This has been an ongoing issue and I have sought help for it more than once. I have even had to add a specific ENV var on a service just to say DEPENDS_ON_STORAGE="${{Storage.RAILWAY_PRIVATE_DOMAIN}}". This feels janky and I feel like a bespoke dependency config pathway for complex multi-service deployment would be a huge asset to the platform. In any case, I'm happy to do whatever to demonstrate the issue - deploying the template, opening a new environment in my example project, just let me know. Thank you!