@lxm : Upon further analysis, we find that you have encountered an issue that appears to be caused by our fix to CBL-6131. I have opened CBL-6534 to track it.