@vegos Should not have been affected by this in any way whatsoever, and I don't see anything of relevance in the logs…
@vegos It was indeed affected, and now the bug is fixed.