Hi @netko,
A fix for this issue was merged in early August and will go out with v3.2. It was not ported to 3.1.1-4, so you’ll need to wait for 3.2.
If you have technical assistance for your journal, you can implement the fix manually by applying the following change: