I think what you’re running into is a known bug with WordPress 6.3.
We have a thread going here with some workarounds: