After duplicating a service, the new deployment appears to be “stuck” on the commit that existed at the moment of duplication. Pushing new commits triggers a rebuild, but Railway still deploys the old, pre-duplication commit—even though the latest code is definitely in the repo. This behavior is consistent across every duplicated service.