When writing/moving files to a Cloudberry Drive mapped to Azure blobs, very randomly (1/100-200 file writes) a file will end up with zero bytes. After exploring the issue, I have found that the Clouberry system will create an empty file very briefly before closing/flushing the write. I’m not sure why some files don’t completely write out on such a rare basis (writing from MS .NET standard I/O methods). We have even encountered cases where 3rd party automatiion systems will read a zero-byte file during the brief instants that the file has been created but is in the un-closed or un-flushed state. I have worked around this problem for critical missions by using Azure blob API systems. These are atomic writes and do not have this problem. But we still have a few areas using Cloudberry drive and may see this zero problem pop up every 2-3 weeks. Other than those rare cases, thousands of files get successfully written with no problem. Is there a solution for this situation other than switching to Azure blob storage API based programs? ( now using version 3.2.0.2 Cloudberry Drive)