Hello Railway Support,

My Railway service domain is serving the latest deployment, but my custom domain is still serving an older deployment.

Service domain:https://composifi-production.up.railway.app/api/runtime/diagnostics

This shows:

• commitSha = d3c70cad4d39a9b701866b0f80ae014fa45e5567
• serverStartedAt = 2026-05-14T03:20:57Z

Custom domain:https://composifi.com/api/runtime/diagnostics

This still shows:

• commitSha = a5094318611c6c347d7a9ba12e756dd09a8c3b32
• serverStartedAt = 2026-05-14T01:40:50Z

The service appears deployed correctly, but composifi.com looks like it is routed to an older running instance, old deployment, or different domain mapping than composifi-production.up.railway.app.

Can you please:

1. Check the custom domain mapping/routing for composifi.com and confirm it points to the same Railway service/deployment as composifi-production.up.railway.app?
2. Confirm whether there are multiple Railway services, environments, or custom-domain mappings attached to composifi.com that could explain why the Railway service URL and custom domain are serving different commit SHAs?

I need https://composifi.com/api/runtime/diagnostics to return:

• commitSha = d3c70cad4d39a9b701866b0f80ae014fa45e5567

This is blocking production QA because I need to verify the live public domain, not only the Railway service URL.