Something is wrong with JSONpath preprocessing, it seemingly uses path values from a different preprocessed item

I see something is terribly wrong with JSONpath preprocessing. We preprocess different values in dependent items, extracting a specific path. The item becomes unsupported, and the error message is very strange.

Preprocessing failed for: {"0":{"32":{"0":{"drive's position":"DiskGroup: 0, Span: 0, Arm: 0","enclosure position":"1","dev...
1. Failed: cannot extract value from json by path "$[0][32][0]["predictive failure count"]": object not found starting with json path: "trnk30233"][1]"

The thing is, the original path to be extracted is [0][32][0] which is perfectly present in the object. But error message shows path of "trnk30233"][1], which is the partial JSON path from a different item residing on different host. Seems like some stale pointer or memory area is erroneously reused in JSONpath preprocessing.

I don't know how to debug this further, any suggestions are highly appreciated.