Conflicts found in the target of the artifacts

Hello,
In several cases of creation release bundles we had strange behaviour.
When we try to use below AQL

items.find({
"$or": [
{
"$and": [
{
"repo": "docker-production",
"$or": [

{ "path": "gvp/gvp_rs/9.0.048.18" }

,

{ "path": "gvp/azure/gvp_snmp/v9.0.040.07" }

,

{ "path": "gvp/gvp_rs_init/9.0.048.18" }

]
}
]
},
{
"$and": [
{
"repo": "helm-production-local",
"$or": [

{ "name": "gvp-rs-9.048.18.tgz" }

]
}
]
}
]
}).include("sha256","updated","modified_by","created","id","original_md5","depth","actual_sha1","property.value","modified","property.key","actual_md5","created_by","type","name","repo","original_sha1","size","path")

we have below errors:

5 Conflicts found in the target of the artifacts. for example: Conflicting target path
'docker-production/gvp/gvp_rs_init/9.0.048.18/sha256__073dba9546e7c02194e87f3ec96d89e19c4f1218cd2c6fbf39570dc91b4e8a9f'
for the following source paths:
'docker-production/gvp/gvp_rs_init/9.0.048.18/sha256__073dba9546e7c02194e87f3ec96d89e19c4f1218cd2c6fbf39570dc91b4e8a9f',
'docker-production/gvp/gvp_rs_init/9.0.048.18/sha256__073dba9546e7c02194e87f3ec96d89e19c4f1218cd2c6fbf39570dc91b4e8a9f'.
Please refer to the debug logs for the full conflict list.

If we exclude the "gvp/gvp_rs_init/9.0.048.18", the resulted AQL works without problems.
If we then create the AQL only for "gvp/gvp_rs_init/9.0.048.18", it also works.

Could you explain how we could handle this problem?

Thank you,
Alexey