I think this is probably the same bug I reported here:
It seems that a fix was already done, but it will arrive in the next version after 23.12.1