@Martin.l I just looked at the attached CBL.zip and I could find anything mentioning about “fd052b01-44ec-4426-896d-cbb17b79802c” doc. In general, if a change (revision) is not successfully sent to SG especially due to the connection issue, it will get retried next time. For this case, if I understand it correct, it doesn’t get retried. To debug this issue, we would need to have CBL logs and SG logs when the issue is reproduced. Otherwise it would be difficult to understand what was going on.
Can you reproduce the issue and re-send the logs at the time that the issue happens?