I have searched for existing issues that may be the same as or related to mine.
Baikal is one of the most popular currently maintained WebDAV solutions. But given that this problem is also happening with the default repo, I don't think this is a Baikal issue.
Potential solution
As suggested in this comment, OpenTasks support would make Orgzly compatible with WebDAV sync tools like DAVx5 and EteSync, without requiring any additional configuration. That way, the actual sync logic is handled by them. Orgzly would simply be using their existing sync backbone automatically by outputting a compatible format.
This would eliminate the need to setup sync specifically for Orgzly as it would be compatible with system-wide sync.
Baikal is one of the most popular currently maintained WebDAV solutions. But given that this problem is also happening with the default repo, I don't think this is a Baikal issue.
Potential solution
As suggested in this comment, OpenTasks support would make Orgzly compatible with WebDAV sync tools like DAVx5 and EteSync, without requiring any additional configuration. That way, the actual sync logic is handled by them. Orgzly would simply be using their existing sync backbone automatically by outputting a compatible format.
This would eliminate the need to setup sync specifically for Orgzly as it would be compatible with system-wide sync.