Hi Janic,
Sorry to hear that you are experiencing this issue.
This is indeed a known issue on our end, and you are not alone in experiencing it as we have it reported by other customers. I can confirm that your case is linked to the main thread addressing this problem internally.
Our engineering team is aware of the issue and is actively working on a solution. In the meantime, the only workaround at the moment is to either make changes solely at the template level and avoid using the Local Override page, or to downgrade to MX 18.1.
Please keep in touch with our support team as they will be able to notify you as soon as a solution is available.
If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution " so that others can benefit from it.