The solution is to enable debug for the sync id which is generating the warning, then examine the /tmp/haast.sync.XXX.debuglog file for details of the warning. If the warning is correct or acceptable then no further action is required. If you wish to eliminate the warning completely you can edit the pre or post-sync script file to remove reference to the data (or correct the file to match your implementation).
