I just experienced the same thing with version 3.11.4. Fortunately, it’s reported as fixed in 3.12.0-beta6.