Hi Daniels,
Welcome to the forum!
We have introduced a fix for this issue in 33 beta 2, but we received a report that it still can happen in particular cases. We’re sorry for all the inconvenience. We’re actively working on it to make sure it doesn’t persist in the stable release. I’ll share any updates as soon as I have them.
For now, if you’re open to it, updating to 33 Beta 2 might help. I know that isn’t ideal, especially with a big deployment coming up. But in this version, we’ve identified that the issue occurs when using the Apply and Start button.
Instead, if you start the log directly from the Logging tab, it should save correctly. If you need to make changes, try applying them first and then restart logging.
Let me know if you’d like any help with this.