Hey @vangelov!
This seems as though it could potentially be related to a known issue our engineers are investigating. Can you try the workaround mentioned here and let us know if that works?