Hi everyone,
We are currently experimenting with cooked data snapshots using a shared Zen server instance.
The shared Zen server contains an already uploaded project and oplog. It was uploaded with the command: zen.exe oplog-export --zen https://sharedzen.example/ --target-project RemoteProject --target-oplog Windows --hosturl http://127.0.0.1:8558 --project LocalProject --oplog Windows
The issue is, if I try to upload the same cooked data to a different oplog within the same project on the shared zen server I am receiving following error:
Error: Failed due to an exception: Failed to save oplog container for oplog 'RemoteProject/Windows_secondOplog': The response for https://sharedzen.example//prj/RemoteProject/Windows_secondOplog is not formatted as a compact binary object
Here is the command that was used to upload the second oplog. Please note, the only difference is the —target-oplog parameter. Cooked data is exactly the same as with the previous upload.
zen.exe oplog-export --zen https://sharedzen.example/ --target-project RemoteProject --target-oplog Windows_secondOplog --hosturl http://127.0.0.1:8558 --project LocalProject --oplog Windows
Is this expected behavior if nothing changed during cook or am I missing something? If I check the remote zen server´s dashboard I can see it actually created the Windows_secondOplog and it even contains the same data as the previous oplog. So to me it seems the upload was successful and that this error is misleading.
UE version: 5.7.4
Zen version: 5.8.0