@ntnsndr sorry about that. Its probably issue on our side - we work on performance improvements that should fix that