Can you confirm whether the duplicated project gets a new public hostname assigned, or whether it's inheriting metadata from the original project?

My first guess would be that the clone operation is copying the database configuration successfully but not fully reprovisioning the public networking resources associated with the original service.

A few things that would help narrow it down:

• Does the generated public URL resolve via DNS?
• Does it return a Railway error page, connection timeout, or NXDOMAIN?
• If you remove and re-add networking on the duplicated project, does the URL start working?
• Does a redeploy fix it, or only creating an entirely new project?

If creating a fresh project consistently works while duplication consistently fails, that points toward the duplication workflow missing a provisioning step rather than a Postgres issue itself.

Would be interesting to know whether this affects all duplicated Postgres projects or only ones created from older templates.