How to ignore a new but identical file?

[nickchomey]

I have a situation in which the same file gets deleted and recreated regularly. The contents rarely change, but when i run rustic backup, rather than just ignore the file, it does a minor sync.

B/s   (ETA -)Files:       0 new, 1 changed, 18733 unchanged
Dirs:        0 new, 7 changed, 657 unchanged
Added to the repo: 353.1 kiB (raw: 453.2 kiB)

The file is actually much larger, so it correctly recognizes that there aren't any changes to the content, but I assume that a different create time etc causes rustic to track some sort of change.

If I do a backup before the file is deleted and recreated, I just get this and no snapshot is created (since I used --skip-identical-parent)

Files:       0 new, 0 changed, 18734 unchanged
Dirs:        0 new, 0 changed, 664 unchanged
Added to the repo: 0 B (raw: 0 B)
processed 18734 files, 97.1 MiB
snapshot 00000000 successfully saved.

My question is whether there's some way to ignore the fact that the same file contents are technically in a new file? I tried --ignore-ctime and --ignore-inode, but those didnt seem to work.

Thanks!