No0bstacles

If that's the case, then yeah, it definitely sounds like it was a timing issue. 

You're very welcome, and I'll let you know as soon as I have feedback from Alex. 

Wow, that issue sure shows up a lot in the service log. 
I've flagged the logs for Alex (the Developer), so he can check.
https://stablebit.com/Admin/IssueAnalysis/27781

It's probably safe to ignore.
Just in case, could you run the StableBit Troubleshooter on the system in question?

http://wiki.covecube.com/StableBit_Troubleshooter
Use "3525" as the Contact ID in the Troubleshooter. 

Larger chunk sizes is a good idea.  But aside from that, the defaults should be pretty good, actually.
And the 63TB thing ... the drive can be larger than that. But if it is, you'd want to partition the drive so that no single partition is larger than that. 
 

The box for the capacity is a text box. You can type on any value you want (that ... is supported, at least, so up to 1PB). As long as your provider has the free space for it. 
 
Just remember that the largest cluster (allocation unit) size may be 64kb on most versions of Windows, which means 256TB volume, max.  
Also, note that you may not want to have partitions/volumes that are larger than 63TBs, as Windows has issues with disk checking if the volume is NTFS and 64TBs or larger...  You can partition and pool the partitions to avoid the issue, if needed... But ....

You're very welcome for it! 
 
And yeah, the larger chunk size means potentially lower overhead, so it's not a bad idea, if this is for multimedia storage.