and possibly you found one, odd as it may seem. Probably needs more testing, so thanks for keeping at it. The first straws some others found involved network errors or maybe other interruptions that went badly…
“Unexpected difference in fileset” errors [2.0.3.9]
Reproducible: Unexpected difference in fileset version X: found Y entries, but expected Z
If you can keep it happening regularly, that will help understand it, but the job probably must add logging to give some trail of how it went badly, for example, –log-file and –log-file-log-level=Information or even more. You can also watch the failure live if it’s predictable enough. Job logs might even already have information.