Hi @Thiago_Conrado
It sounds like you may be experiencing the same issue that’s described here:
If so - we’re working on a fix now.