Behavior of ETL unresolvedLinkAction

I’m running into some behavior I don’t understand with respect to unresolvedLinkAction. I’m trying to load TireFItments, some of which (but not all) have corresponding TirePluses with the sameCarTireId. It seems like TirePlus vertexes are being created when a corresponding one does not exist, despite the fact that I’m using “unresolvedLinkAction” : “HALT”

Here is my config:

{
    "config": {
        "log": "debug"
    },
    "source": {
        "file": {
            "path": "..\\\..\\TireDataOrientDataLoad\\Tire_Fitment_data.json"
        }
    },
    "extractor": {
        "json": {}
    },
    "transformers": [
        {
            "vertex": {
                "class": "TireFitment"
            }
        },
        {
            "edge": {
                "class": "hasPlusSize",
                "joinFieldName": "CarTireId",
                "lookup": "TirePlus.CarTireId",
                "unresolvedLinkAction": "HALT",
                "skipDuplicates": false
            }
        }        		
    ],
    "loader": {
        "orientdb": {
            "serverUser": "root",
            "serverPassword": "${server_password}",
            "dbURL": "remote:127.0.0.1/tires",
            "dbUser": "admin",
            "dbPassword": "${db_password}",
            "dbAutoDropIfExists": false,
            "dbAutoCreate": true,
            "dbAutoCreateProperties": true,
            "standardElementConstraints": true,
            "tx": false,
            "wal": false,
            "batchCommit": 1000,
            "dbType": "graph",
            "classes": [
                {
                    "name": "TireFitment",
                    "extends": "V"
                },
                {
                    "name": "hasPlusSize",
                    "extends": "E"
                }
            ],
            "indexes": [
...
            ]
        }
    }
}