Why does call caching miss even when inputs are identical?
I'm stuck on a problem where call caching reproducibly works early in one of my workflows, and then consistently fails to find a hit for a specific task. The hashes in the call info from the metadata show that it's one particular input file whose hash always changes. I don't understand how this is possible considering that the file contents are identical between runs - it's just a symlinked output of a previous task that was successfully retrieved from the cache. This occurs with multiple configurations of duplication-strategy and hashing-strategy, and so far no matter what I try it always changes the hash for this file. Is there some subtlety to how repeated calls are detected and I'm screwing it up?