Nextcloud creating new files one directory below original location during sync on Mac OS

Hi,
We have been using next cloud for a while and I just started to use it for sharing lots of files we collect for analysis. Maybe close to 10,000 files. We have had an issue happen twice where the Nextcloud service or Mac client (not sure who starts the event) but we get copies of the files one level down in the directory tree. For example if our filesystems looks like this -

foo
foo/logs
foo/logs/client1
foo/logs/client1/2018-05-20/subdir1
foo/logs/client1/2018-05-20/subdir1/file1
foo/logs/client1/2018-05-20/subdir1/file2
foo/logs/client1/2018-05-20/subdir1/file3
foo/logs/client1/2018-05-20/subdir2
foo/logs/client1/2018-05-20/subdir2/file1
foo/logs/client1/2018-05-20/subdir2/file2
foo/logs/client1/2018-05-20/subdir2/file3
foo/logs/client1/2018-05-20/subdir3
foo/logs/client1/2018-05-20/subdir2/file1
foo/logs/client1/2018-05-20/subdir2/file2
foo/logs/client1/2018-05-20/subdir2/file3
foo/logs/client1/2018-05-21
foo/logs/client1/2018-05-21/subdir1
foo/logs/client1/2018-05-21/subdir2
foo/logs/client1/2018-05-21/subdir3
foo/logs/client1/2018-05-22, …etc for 10’s more directories
foo/logs/client2
foo/logs/client2/2018-05-20
… again similar structure for 10’s more directories

What happens is that we get copies of the directories at the date level from client1 created at the foo/logs directory level.

This has happened twice, the first time it was not clear what caused the issue, the second time this occurred we stopped it by disabling sync on the Mac. The Mac client was syncing the foo/logs directory and displaying messages such as ‘checking subdir1 for changes’ and was taking a long time. Nothing was copied to the local directory on the mac but in the server copies of 2018-05-20/subdir1 were being created at foo/logs directory level.

I just found out that an admin moved the foo directory to a new location on the server, could that be the cause of the strange sync behavior?

Is this the correct place to file a bug? This is a real issue and it repeatable. If someone wants me to collect more information before we delete the entire mess and use a different solution let me know.

Thanks