We have a ivy module which happens to have multiple artifacts with the same sha1 values. Since upgrading to artifactory 126.96.36.199, when a build is promoted, these artifacts are not copied/moved from the source repository to the target repository. Previously, all the artifacts of the build were copied/moved as expected.
Workaround is to force the sha1 to be different or manually copy these artifacts after our promotion process. This is causing significant additional work for us when promoting a build as we currently cannot make these artifacts have different sha1 values.