"jf rt del" on conan repo causes 404 errors

Hello
Artifactory 7.71.23

Every night I am deleting old conan packages from my development remote

I am running jf rt del --spec ArtifactoryRetentionPolicy.json

my retention spec looks like this:

{
  "files": [
    {
      "aql": {
        "items.find": {
          "$or": [
            {"repo": "my-development-local"}
          ],
          "type": "file",
          "path": { "$match": "*" },
          "created": { "$before": "5d" }
        }
      }
    }
  ]
}

Often the operation fails like this:

01:13:17 [Error] server response: 404 Not Found
{
  "errors": [
    {
      "status": 404,
      "message": "Could not locate artifact 'my-development-local:_/gtest/1.8.1/_/3b48eb3c3f93c777d5303b27a6397eb4/package/21f1970cf8e93e5f6c813d46eb065f983f20061a/index.json' (Nothing to delete)."
    }
  ]
}
01:13:17 [Info] Trace ID for JFrog Platform logs: 9d8e84355f9f0f67
01:13:17 [Error] server response: 404 Not Found
{
  "errors": [
    {
      "status": 404,
      "message": "Could not locate artifact 'my-development-local:_/gtest/1.8.1/_/3b48eb3c3f93c777d5303b27a6397eb4/package/21f1970cf8e93e5f6c813d46eb065f983f20061a/index.json' (Nothing to delete)."
    }
  ]
}

Is this not the way to go when deleting expired conan packages on artifactory?

Regards
Klaus

Start by reproducing jf rt del --spec ArtifactoryRetentionPolicy.json against an Artifactory Conan repository using the AQL spec and artifact path shown in the report. Trace the delete command's handling of Conan package paths and 404 responses; done means the reported retention operation behaves correctly for expired packages or the limitation is clearly documented.