Thank you for the feedback! The issue was previously already resolved, but seems to be back again. Will be fixed soon, when the next patch is ready.

(edit 23/9/2025): Version 1.6 has been rolled out yesterday, the issue has been resolved.