Thank you for the confirmation. It does seem like then this issue is related to the known issue I mentioned that was just uncovered.
As I suggested earlier, if it’s not an issue I would stick with the 3.12.0 for now until we can investigate and resolve this issue on our side.
Best Regards,
Jeremias